-
Notifications
You must be signed in to change notification settings - Fork 238
Tuple index out of range error #22
Comments
This error seems to mean one of the model files could be truncated. |
Did that. Same error though.
|
Could you provide the output of |
got the same problem after last update, reinstall didn't help. don't really think it's conflicting with something, but anyway |
Same issue here. Doesn't look like it's being caused by any of the extensions, because I tried disabling all of the other ones. Commit hash: 44c46f0ed395967cd3830dd481a2db759fda5b3b |
I made a brand new auto installation and had the same issue. Here is what I got when first installing:
Afterwards I restarted the webui and Tagger gives the same error as always. So I'm thinking it's a problem with one of the requirements for the extension, or maybe something a different extension installed on the system conflicting with it? Any clues on how to clean up the system of all of that? |
Ok, so I seemed to have found a solution to the first problem! After you unpack it, you'll want the files:
Next, navigate to your Now run the webui bat, and it should work! At least it did for me, so I hope it does for you too. |
I removed the cache and PIP package from my Windows and Linux environment and tested it after clean installation, but this bug could not be reproduced. And the code itself doesn't seem to be a problem. Is there a problem with the HuggingFace? I'm trying to find a way to fix it. If you need to use it right now, use the ee167ea. |
I've been trying to break my own venv, trying various versions of Tensorflow between 2.9 - 2.11 (the models were trained using TF 2.10.0), redownloading the weights from HF multiple times, etc. Yet so far, I haven't managed to reproduce the error. Assuming something went wrong with the serialization of the model (yet most users seem to be ok?), could anybody with a broken setup try and put the Mind you: all other files MUST be the ones from HuggingFace, not the ones from the MEGA zip. |
Just replacing that one file didn't work but manually copying all the blob files to the correct locations and renaming them to the proper filenames did in fact work. Symlinks on windows are rather new so there may be conflicting registry settings. Or windows is just being windows. Note that copying a file named the same as symlink seems to send it to the great beyond. It doesn't replace the symlink with the file. |
That's it! @a1270 you da man! So all the users with problems are launching a command shell as admins, HF hub is creating symlinks, and subsequent reads from TF/Keras in load_model fail to follow the symlink back to the original file. Meanwhile, I was launching the shell as a normal user, so no symlink, because HF hub was downloading files right into the final directory as per https://huggingface.co/docs/huggingface_hub/how-to-cache, and no problems. So the immediate fix is to NOT run the shell as Administrator. EDIT: narrowed it down to |
Did some more digging:
So, two solutions:
Please note, Administrator or not, you're getting models on CPU anyway if you don't roll back your TF installation to v2.10. There's also the possibility of completely forgoing TF's nonsense and switch to ONNXRuntime, but you lose access to the official DeepDanbooru models and have to rely on third party's conversions. |
Of course I don't mind using ONNX. However, converting DeepDanbooru to ONNX is an individual model maker's choice, and explaining how to convert it to users will be too complicated. So I think it would be better to support ONNX additionally. Using Torch, Tensorflow and ONNX together in one program is a bit silly, but I think this is the best. Thank you all for your help! If there is anything that can be improved, don't hesitate to let me know! |
file got removed...
Where can I find this variables file? |
Found the file and it worked! I will say I don't run the webUI as admin, so I'm not sure what caused this issue. |
I modified it to use ONNX as recommended by @SmilingWolf. If it works well, I'll close the issue. |
I am still having this issue and the above linked files are no longer available |
Make sure you're on the latest version of the extension and post the full log from the console. |
There seems to be no additional problem, so I'll close the issue. |
Getting this error after updating to latest commit:
The text was updated successfully, but these errors were encountered: