-
-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[active_job] support exception reporting only after last retry failed #2573
base: master
Are you sure you want to change the base?
Conversation
4ab9ff9
to
b26b17a
Compare
90144c4
to
2fa01fc
Compare
2fa01fc
to
d19050a
Compare
d19050a
to
36c1176
Compare
Please ignore Danger here, it just fails to see that I added CHANGELOG entry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Left some suggestions for tests.
@@ -52,6 +54,10 @@ | |||
expect(Sentry::Rails::Tracing.subscribed_tracing_events).to be_empty | |||
Sentry::Rails::Tracing.remove_active_support_notifications_patch | |||
|
|||
if defined?(Sentry::Rails::ActiveJobExtensions) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think with our current setup this will always be true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@st0012 not really, it may or may not be defined, depending on the order of loading files which is pretty much random 🙃
Otherwise specs would be failing randomly
36c1176
to
4e59569
Compare
Instructions and example for changelogPlease add an entry to Example: ## Unreleased
- [active_job] support exception reporting only after last retry failed ([#2573](https://github.com/getsentry/sentry-ruby/pull/2573)) If none of the above apply, you can opt out of this check by adding |
dc38bb6
to
4e59569
Compare
This is an updated version of #2500 which adds support for
active_job_report_after_job_retries
option which makes reporting an exception upon a job failure to happen only on the last attempt retry failure.