🐛 fix: stop sentry app tasks from emitting NoRetriesRemainingErrors#98292
Conversation
| raise_on_no_retries=False, | ||
| ) |
There was a problem hiding this comment.
Potential bug: Adding raise_on_no_retries=False causes tasks to fail with RetryError instead of being silently ignored, contradicting the intended 'fire and forget' behavior.
-
Description: Adding
raise_on_no_retries=Falseto theretry_decoratorchanges the exception raised upon exhausting retries fromNoRetriesRemainingErrortoRetryError. The task's exception handling is configured to silently ignoreNoRetriesRemainingErrorbut re-raisesRetryError. This change unintentionally alters the behavior of these 'fire and forget' tasks, causing them to fail loudly with aRetryErrorwhen all retries are used up, instead of failing silently as intended. This leads to unexpected task failures. -
Suggested fix: To restore the intended 'fire and forget' behavior, either add
RetryErrorto theignoretuple in theretry_decoratoror remove theraise_on_no_retries=Falseparameter to revert to the previous exception-raising behavior.
severity: 0.55, confidence: 0.95
Did we get this right? 👍 / 👎 to inform future reviews.
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #98292 +/- ##
==========================================
- Coverage 81.01% 80.98% -0.03%
==========================================
Files 8562 8567 +5
Lines 376457 376806 +349
Branches 24123 24123
==========================================
+ Hits 304982 305157 +175
- Misses 71094 71268 +174
Partials 381 381 |
these sentry app tasks are "fire and forget"/ best effort tasks to send a payload to a sentry app. if the service on the sentry app side is down, we can't do much and emitting the exception causes extra noise we don't need.
lets ignore them.