You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When resuming downloads, snapshot_download handles errors [requests.exceptions.ConnectionError, requests.exceptions.Timeout, huggingface_hub.errors.OfflineModeIsEnabled, requests.HTTPError]
(e.g., Hub downtime) by falling back to locally cached files without raising an error. This occurs because the code prioritizes cache availability over server communication status
Hi @NearBirdEZ, can you elaborate on what's your expectation for this vs what you currently have? Falling back to existing cache instead of raising an error is actually a feature implemented on purpose, not a bug. If you've spotted a bug in a specific case, please let us know precisely.
Hi, @Wauplin
Today, for example, the loading of the model was interrupted due to the 500 error HF
After that, I tried to restart, and instead of the expected model before loading, or the error that the server is unavailable, I got, in theory, the result that the entire model is available, here is the path.
It turns out that if the download is automated and without close attention, it may be that there will be an attempt to work with incomplete data
Yes indeed, you are correct. When implementing things, we took the decision that the benefit of returning a local cache outweighs the drawback of potentially returning a half-empty folder. It's not perfect but it's a compromise that we knowingly chose to take. So not a bug and not really something we want to iterate on at the moment. If we see strong interest on that topic in the future, we might re-evaluate.
Describe the bug
Description
When resuming downloads,
snapshot_download
handles errors[requests.exceptions.ConnectionError, requests.exceptions.Timeout, huggingface_hub.errors.OfflineModeIsEnabled, requests.HTTPError]
(e.g., Hub downtime) by falling back to locally cached files without raising an error. This occurs because the code prioritizes cache availability over server communication status
Reproduction
Logs
System info
The text was updated successfully, but these errors were encountered: