S3 Retry Option Bindings - #764
Merged
Merged
Conversation
TingDaoK
reviewed
Sep 10, 2026
TingDaoK
reviewed
Sep 10, 2026
TingDaoK
approved these changes
Sep 10, 2026
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
2 participants
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.
Add
S3RetryConfigdataclass to s3.py as an optional S3 client configuration allowing the assignment of the following members:max_retries
backoff_scale_factor_ms
max_backoff_secs
jitter_mode
initial_bucket_capacity
Any options that are not set will use their S3 default values.
Moved
ExponentialBackoffJitterModefrom mqtt5.py intoio.pyas it is now shared across both mqtt and s3By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.