Repository navigation
馃悰 fix(standalone): retry index fetch, resume dropped downloads - #2001
Merged
Merged
Conversation
gaborbernat
force-pushed
the
download-retries
branch
from
August 12, 2026 19:26
0862118 to
47cd1cc
Compare
gaborbernat
force-pushed
the
download-retries
branch
from
August 12, 2026 21:13
47cd1cc to
df5f866
Compare
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.
Transient GitHub errors abort standalone-Python fetches: the release-index
urlopenhas no retry, and the archive retry covers only opening the connection, soRemoteDisconnected/IncompleteReadmid-body escapes it (run 31618954128). Both fetches now retry with exponential backoff on connection errors and 429/5xx; 4xx raises immediately. A dropped archive download resumes from the bytes already on disk with aRangerequest, falling back to a clean restart when the server ignores it.