Bump sentry-ruby from 5.8.0 to 5.9.0

Bumps sentry-ruby from 5.8.0 to 5.9.0.

Changelog

5.9.0

Features
Add new boolean option config.enable_tracing to simplify enabling performance tracing #2005

config.enable_tracing = true will set traces_sample_rate to 1.0 if not set already

config.enable_tracing = false will turn off tracing even if traces_sample_rate/traces_sampler is set

config.enable_tracing = nil (default) will keep the current behaviour
Allow ignoring excluded_exceptions when manually capturing exceptions #2007

Users can now ignore the SDK's excluded_exceptions by passing ignore_exclusions hint when using Sentry.capture_exception.
# assume ignored_exception.class is included in config.excluded_exception
Sentry.capture_exception(ignored_exception) # won't be sent to Sentry
Sentry.capture_exception(ignored_exception, hint: { ignore_exclusions: true }) # will be sent to Sentry
Support capturing low-level errors propagated to Puma #2026

Add spec to Backtrace::APP_DIRS_PATTERN #2029

Forward all baggage header items that are prefixed with sentry- #2025
Add stackprof based profiler #2024

The SDK now supports sending profiles taken by the stackprof gem and viewing them in the Profiling section.

To use it, first add stackprof to your Gemfile and make sure it is loaded before sentry-ruby.
# Gemfile
gem 'stackprof'
gem 'sentry-ruby'
Then, make sure both traces_sample_rate and profiles_sample_rate are set and non-zero in your sentry initializer.
# config/initializers/sentry.rb
Sentry.init do |config|
config.dsn = "<dsn>"
config.traces_sample_rate = 1.0
config.profiles_sample_rate = 1.0
end
Some implementation caveats:

Profiles are sampled relative to traces, so if both rates are 0.5, we will capture 0.25 of all requests.

Profiles are only captured for code running within a transaction.

Profiles for multi-threaded servers like puma might not capture frames correctly when async I/O is happening. This is a stackprof limitation.

... (truncated)

Commits

6f1b9ad release: 5.9.0
78a4cb7 Changelog for 5.9.0 (#2034)
d63b77a Support capturing low-level errors propagated to Puma (#2026)
7fd714e Add stackprof based profiler (#2024)
bad263c Add spec to Backtrace::APP_DIRS_PATTERN (#2029)
d45f720 Allow Sentry.register_patch to take patch and target directly (#2028)
4275d29 Improve Rails 7 example app (#2027)
9a967d2 ref: Forward all sentry- baggage items (#2025)
00ba859 Tweak #2007 and add changelog for it (#2023)
1a2d682 Allow ignoring excluded_exceptions when manually capturing exceptions (#2007)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

ZeusWPI / Gandalf

Bump sentry-ruby from 5.8.0 to 5.9.0 #708

5.9.0

Features