I’m trying to download blip2 in colab local runtime and while the model is downloading and it’s showing in the cache, it’s not showing any progress bar. I wonder why?
No tqdm in there…no way.
Sorry to be so vague, but even when I’m making things for myself, it kind of comes and goes…progress bar. I’m not aware of having changed anything in particular.
Update: I ended up downloading the model through command line instead of colab and the progress bar did show up. Tdqm is installed so I guess it’s something with colab or my jupyter installation
1 Like
The model worked just fine in local runtime as in hosted runtime so I don’t even know
Well, I guess I’m just glad it’s not a VM-specific problem with HF.
I’m not sure if it’s a VM-wide problem, or if Colab and HF’s settings happen to be broken in the same way, or if any of the libraries in the dependencies are the culprit…
Personally, I suspect one of the libraries, because even if we limit it to HF’s Gradio’s Spaces, the progress bar may or may not show up depending on the Spaces.
There are too many libraries that I use regularly to know which one it is.
new update: after switching from python 3.10.6 to 3.11.9 the progress bars appeared, just there is a warning for IProgress which I guess makes the progress bar green in colab hosted runtime
The Python version I’m using is generally local 3.9, HF Spaces default 3.10, but the progress bar comes and goes.
If it just doesn’t appear in older versions, it could be a bug caused by using a syntax in the library that is not supported in older versions of Python…
I wonder if it’s a dependency with some other library that isn’t tqdm? In any case, I think it’s a bug in the sense that the library creator didn’t expect it to work the way it does.
There is no boundary between a bug, a specification, and normal operation…
A program only works as written if you’re lucky.
@Wauplin I’m contacting you because I wonder if the download progress display from HF in from_pretrained is also under the jurisdiction of HF Hub. I don’t know who to report it to.
This is not a serious bug per se, but the scope of the potential impact is unknown.