-
Notifications
You must be signed in to change notification settings - Fork 94
feat: add retry backoff for connection errors in retryOperation #775
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
Open
leshniak
wants to merge
8
commits into
Expensify:main
Choose a base branch
from
callstack-internal:feat/retry-backoff-connection-errors
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+201
−11
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
58d2a8c
feat: add backoff constants and helpers for retry delay
leshniak 16aef2e
feat: add exponential backoff delay to non-capacity error retries
leshniak bf9cf5f
test: update retry tests for backoff and add backoff-specific tests
leshniak bb8e0c2
fix: guard getRetryDelay against negative values
leshniak 0bb1227
Add observability logging for backoff experiment outcomes
leshniak 376a6ba
Fix CI failures: lint early-return, undefined .then(), rebuild docs
leshniak 2430f84
Run prettier on changed files
leshniak bc0b381
Move ts-expect-error to correct line inside Promise.resolve callback
leshniak File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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
Oops, something went wrong.
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.
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.
The new recovery log is emitted whenever
onyxMethod(defaultParams, nextRetryAttempt)resolves, butretryOperation()itself resolves even after exhausting all retries, so a permanently failing connection error will still produceConnection error recovered...before/alongside the exhaustion alert. In practice this creates false-positive recovery telemetry for the experiment and can mislead rollout decisions, because exhausted retry chains are counted as successful recoveries.Useful? React with 👍 / 👎.
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.
This sounds valid in the case where we fail multiple times rather than just once?