Repository navigation
Conversation
franz101
changed the title
franz101
force-pushed
the
fix/xet-download-stall
branch
3 times, most recently
from
October 30, 2026 16:12
8eda890 to
6be111e
Compare
franz101
marked this pull request as draft
October 30, 2026 16:14
Author
|
Draft until it's fixed in xet-swift |
franz101
force-pushed
the
fix/xet-download-stall
branch
from
October 30, 2026 16:26
6be111e to
f4e903c
Compare
franz101
changed the title
swift-xet waits 120 s on a silent xorb fetch before retrying it, but the download watchdog stopped the whole attempt after 60 s without progress. One slow range near the end of a multi-gigabyte shard therefore restarted every file from zero, and after three attempts the download failed with "stopped responding after multiple automatic retries". Time out silent fetches after 30 s and retry sooner so swift-xet recovers on its own, and give the watchdog room for its backoff. Each stopped attempt also left its uniquely named .incomplete file behind, because huggingface_hub only removes it when Python unwinds; the helper now deletes its partial file when it is terminated.
swift-xet 1.1.1 refreshes presigned xorb URLs that expire during long downloads, and starts a fetch's retries over while it keeps making progress. Drop the shorter read timeout and retry delay, which on a slow link made healthy fetches retry, and keep partial files when the helper is terminated so an interrupted download can be resumed.
franz101
force-pushed
the
fix/xet-download-stall
branch
from
November 1, 2026 23:17
f4e903c to
d686ed2
Compare
Author
|
The fix of huggingface/swift-xet#28 got merged in xet-swift 1.1.1 |
franz101
marked this pull request as ready for review
November 1, 2026 23:44
This branch has not been deployed
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.
Problem
Large Xet-backed downloads (e.g.
dima6312/Flint-40B-A2.5B-abliterated-MLX-4bit, nine ~4.7 GB shards) failed with "The model download stopped responding after multiple automatic retries."Fix
read_timeout.Earlier revisions also shortened swift-xet's read timeout and retry delay, and deleted the partial file on SIGTERM. Both are dropped. With 1.1.1, the shorter timeouts only add retries on slow links. The partial file is needed to resume (#796).
Testing
HuggingFaceDownloadCapacityTestsandLocalModelProviderTestspass.mlx-community/Qwen3-32B-4bit(18.4 GB) on a ~12 MB/s connection:mainfailed after 59 min on its first attempt, with no shard complete. That is about when the xorb URLs expire.