-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
won't run without network connection #171
Comments
Oh I see it says downloading every time. I dug into it and looks like a bug in huggingface-hub. Will fix. |
When you've fixed this bug please consider informing the community that the initial download is 4.27GB. That's not nothing. If there's a way to remove this data when we're housecleaning our computers that would be sweet indeed. |
@johnblommers the requirements already state
|
I've made a pull request into the hugging-face hub library to fix this. If that's not fixed in a timely fashion I can make a workaround. huggingface/huggingface_hub#1306 |
12 hours wasn't fast enough. just released 8.0.5 has fix/workaround. |
Um, I still have this problem and run current versions… is this fixed, a different bug, or am I holding it wrong? Problem: Error: Context: |
On first generation with a model, it of course has to download the weights. If you're saying that the weights were already downloaded, I'll look into it more. |
yes, the weights are definitely downloaded and locally available. should be easily reproducible, at least in my case, i can't generate anything at all when offline, just aborts throwing this error. if helpful: if i start my program while online and generate an image, then kill the internet connection while my code is still running, i can still keep generating. however if i now (while offline) stop and restart my program, it fails. |
even if model/config etc in cache..
found this one accidentally..
7.6.0 (OSX, Python venv 3.10.8)
I noticed recently that the first step is always (well what's output to console anyway) to go to the network to download model even when model is in cache.. not sure if this logic was changed at some point or for some reason..
Ideally of course : cache check first, then get model from network, and if network fails a graceful exit with error message..
thanks for all the latest adds + fixes!
The text was updated successfully, but these errors were encountered: