Repository navigation
Retry transient S3 errors with bounded backoff - #46
Draft
joshfriend wants to merge 1 commit into
Draft
joshfriend wants to merge 1 commit into
joshfriend wants to merge 1 commit into
Conversation
Signed-off-by: Josh Friend <josh@fueledbycaffeine.com>
joshfriend
force-pushed
the
jfriend/s3-server-retries
branch
from
October 21, 2026 13:58
90035ec to
b71092d
Compare
joshfriend
changed the title
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
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.
Retry transient S3 server errors on downloads and uploads up to three attempts with cancellable exponential backoff and jitter, without adding the AWS SDK. This is an alternative to #45. Network errors and partially consumed response bodies are not retried.