mirror of
https://github.com/DominikDoom/a1111-sd-webui-tagcomplete.git
synced 2026-11-05 00:17:25 +00:00
[GH-ISSUE #205] Still getting errors on launch: Error loading script: tag_autocomplete_helper.py #147
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#147
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 @vt-idiot on GitHub (Jul 23, 2023).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/205
@vt-idiot commented on GitHub (Jul 23, 2023):
I was able to fix it with a pretty simple
mkdir -p /content/stable-diffusion-webui/tmp/- now I only see the expectedTag Autocomplete: Could not locate model-keyword extension, LORA/LYCO trigger word completion will be unavailable.while launching.@yo1nkers commented on GitHub (Jul 23, 2023):
Hi, is the current issue you're experiencing
Tag Autocomplete: Could not locate model-keyword extension, LORA/LYCO trigger word completion will be unavailable.causing you any major issues? This is currently the issue I am getting, and I am looking for a fix to this.
@DominikDoom commented on GitHub (Jul 23, 2023):
@vt-idiot Yeah thanks for the reminder, I forgot that this folder isn't there by default on Linux since the webui creates it to store stderr/stdout logs on windows. This was a very early issue with #46 and I missed that when restructuring the path declarations.
@yo1nkers Is this unexpected for you or preventing normal completion from working? If you just see that message but nothing else, all it means is that the keyword lists weren't found. It's just an info message so people know why the feature would be unavailable in that case.
@vt-idiot commented on GitHub (Jul 24, 2023):
@yo1nkers nope, I imagine it'd go away if I installed the
model-keywordextension and filled out the keyword lists, sounds like it lets you fill out activation tags for all your LoRA?The handful of LoRA I use with activation tags already had presets saved directly in webui, and also in the metadata for their thumbnails in the browser, so I just use those.
@DominikDoom commented on GitHub (Jul 24, 2023):
Exactly, if you don't want to use it you can just ignore the message. Since some seem to think of it as a critical error I will maybe reword or remove the hint in the future though.
The list of model keywords provided by that extension is pretty big and auto updated from civitai, so it was a good way to not have to support and ship my own list.
The README has a new section about it that goes into detail.
@brehuang commented on GitHub (Jul 26, 2023):
Having the same issue. This seems to have coincided with the new release of automatic1111, since I didn't have this issue yesterday. I can't use Latent Couple anymore. If anyone has a solve, please share.
@DominikDoom commented on GitHub (Jul 26, 2023):
@brehuang What issue exactly are you talking about? The error in the first comment here which was already fixed, or the "Could not locate model-keyword extension" info message which is harmless?
This extension is not affected by the new webui release as far as I'm aware, so anything else will be unrelated (assuming tag-autocomplete is up to date too)