Issue Description
After the update to version 5.1.0 I started to get Sidekiq::JobRetry::Skip errors in Sentry. After close examination, I found that for each of these errors I also had their cause reported as a separate error in Sentry.
It seems the Sidekiq error handler:
|
config.error_handlers << Sentry::Sidekiq::ErrorHandler.new |
is creating the sentry error for the cause, and the new error subscription for version 5.1.0:
|
app.executor.error_reporter.subscribe(Sentry::Rails::ErrorSubscriber.new) |
is creating the sentry error for the Sidekiq::JobRetry::Skip
Reproduction Steps
Use the 5.1.0 version of Sentry and raise an error within a sidekiq job.
Expected Behavior
The raised error should be logged in Sentry
Actual Behavior
Two errors are logged in sentry:
- The raised error
- The Sidekiq internal
Sidekiq::JobRetry::Skip
Ruby Version
3.1.0
SDK Version
5.1.0
Integration and Its Version
Rails (7.0.2) + Sidekiq (6.4.1)
Sentry Config
I don't have any custom error handling configured
Issue Description
After the update to version
5.1.0I started to getSidekiq::JobRetry::Skiperrors in Sentry. After close examination, I found that for each of these errors I also had their cause reported as a separate error in Sentry.It seems the Sidekiq error handler:
sentry-ruby/sentry-sidekiq/lib/sentry-sidekiq.rb
Line 28 in 623d046
is creating the sentry error for the cause, and the new error subscription for version
5.1.0:sentry-ruby/sentry-rails/lib/sentry/rails/railtie.rb
Line 123 in 623d046
is creating the sentry error for the
Sidekiq::JobRetry::SkipReproduction Steps
Use the
5.1.0version of Sentry and raise an error within a sidekiq job.Expected Behavior
The raised error should be logged in Sentry
Actual Behavior
Two errors are logged in sentry:
Sidekiq::JobRetry::SkipRuby Version
3.1.0
SDK Version
5.1.0
Integration and Its Version
Rails (7.0.2) + Sidekiq (6.4.1)
Sentry Config
I don't have any custom error handling configured