-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sidekiq exception handlers now take three arguments (DEPRECATION since sidekiq 7.1.5, will become error in 8) #804
Comments
Hi @timdiggins |
This was addressed in #796 and released in 6.26.1. |
As far as I can tell, the deprecation warning is still displayed in 6.26.4.
and in sidekiq check this still has arity == 2
|
Hi @pic Apologies for the delay in response. Can you please confirm whether you are still seeing this warning being displayed when using a Please let us know if you are still seeing this deprecation warning. It would be useful to see the version of |
Hi @mclack We are using 6.27. As far as I can tell you this declaration:
is considered of arity 2, I guess because of the default value. For comparison, I've just noticed how newrelic handles this:
Thx |
Hi @pic, If the reproduction might contain anything sensitive, please feel free to share it with us at support@bugsnag.com instead. |
Still displaying the deprecation warning. |
Hi @pic Unfortunately without a reproduction example of the case we are unable to investigate this issue further. |
Describe the bug
Sidekiq has (since 7.1.5) changed the api for its exception handlers.
https://github.com/sidekiq/sidekiq/blob/main/Changes.md#715
Steps to reproduce
Use a version of sidekiq since 7.1.5 (e.g. 7.2.0 which is latest as of date of writing).
Execute a Sidekiq job with an error like
it will output
Environment
The text was updated successfully, but these errors were encountered: