This repository was archived by the owner on Oct 15, 2026. It is now read-only.
Repository navigation
fix(aws): retry R2's 503s as the other mirrors do - #15
Merged
Merged
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
tlnet's
aws.confighad no retry settings, so the CLI used legacy mode with 5 attempts; gnu, nongnu and ctan useretry_mode = standardandmax_attempts = 10. R2 answered the gnu/nongnu fills with occasional 503s, and lib v2.4.0's one-time relabel (katoptra/lib#17) issues ~15k server-side copies here in one run.Merge order: safe now. Once v2 moves to v2.4.0 I'll push the render update to this branch; merge after that, or merge now and take the render as its own PR.
Test plan:
task checkpasses against today's v2.