mirror of
https://github.com/DominikDoom/a1111-sd-webui-tagcomplete.git
synced 2026-11-05 00:17:25 +00:00
[GH-ISSUE #121] Sudden fail of the extension, after updating other extensions. #90
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
low priority
low priority
pull-request
question
waiting for feedback
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
DominikDoom/a1111-sd-webui-tagcomplete#90
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mart-hill on GitHub (Feb 2, 2023).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/121
After I updated
dreambooth,pix2pix,UmiAIandadditional-networks, tagcomplete started throwing this error:It probably has to do something with WebUI failing to run after these 4 extensions were updated (I'm on 226d840e84c5f306350b0681945989b86760e616 WebUI commit, latest at the moment) - I had errors immediately after fully re-running the UI. So I upgraded
pipin venv (new version just appeared), and also disabled--skip-version-checkin the UI's .bat file, since I think one of these four extensions required something newer. It worked, WebUI started working again, but your extension now is having trouble.Since you explained me the severity of that option at the time - I didn't touch tagcomplete options, it was normally working, until I restarted the UI.
Should I edit some setting again?
I hope I explained it fairly well... 🙂
@MrGrey7 commented on GitHub (Feb 2, 2023):
Can confirm, I get the same error after installing UmiAI and updating pix2pix.
Disabling the extensions and restarting the UI doesn't help.
@ctwrs commented on GitHub (Feb 2, 2023):
I'm able to repro by adding an empty group to a yaml file. Not really sure why it's happening for some users but I can safely log the issue without having it fail autocomplete. Working on it.
@mart-hill commented on GitHub (Feb 2, 2023):
Thank you, it even seems to pinpoint the "culprit"! 🙂