chore(issues): Add LoggedRetry to log retry information #94840
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This gives us visibility into when and why retries are happening, currently we are only able to see that a set of requests (which may or may not have contained retries) succeeds or fails but not individual retry information. This also enables logged retries for seer requests.
github-actions
bot
added
the
Scope: Backend
Codecov ReportAttention: Patch coverage is ✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## master #94840 +/- ##
=======================================
Coverage 87.88% 87.88%
=======================================
Files 10441 10443 +2
Lines 603755 603814 +59
Branches 23505 23505
=======================================
+ Hits 530620 530688 +68
+ Misses 72768 72759 -9
Partials 367 367 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This gives us visibility into when and why retries are happening. Currently we are only able to see that a set of requests (which may or may not have contained retries) succeeds or fails but not individual retry information.
This also enables logged retries for seer requests.