-
Notifications
You must be signed in to change notification settings - Fork 40
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
ComposableLora & Cutoff Extensions not working with Krita Plugin #138
Comments
Whats the commit version for webUI? I'm aware at some point the script API changed. But also, can you check the error does not occur when using the webUI? |
Doesn't happen on WebUI, I have no errors with WebUI. (The Krita dockers are much cleaner btw - I am only recently coming back to this extension, it's really nice to use, great job) |
Hm, so LoRAs might be an always enabled script that injects into script args. When the frontend makes the API request, it wouldn't know the script args for LoRA. I guess the easiest way would be to detect for the LoRA script in my backend and just set it to always be enabled in the frontend. |
Can confirm. That extension was the issue. After disabling it, I ran into a new error with the 'cutoff' extension
I think this lowers the priority of this issue quite a bit. Good catch @rexelbartolome . Thanks for reading / following up @Interpause |
Updating Issue title to be more accurate. |
Error running process: \stable-diffusion-webui\extensions\stable-diffusion-webui-composable-lora\scripts\composable_lora_script.py
Traceback (most recent call last):
File "\stable-diffusion-webui\modules\scripts.py", line 417, in process
script.process(p, *script_args)
TypeError: ComposableLoraScript.process() missing 3 required positional arguments: 'enabled', 'opt_uc_text_model_encoder', and 'opt_uc_diffusion_model'
To Reproduce just put any Lora in your Krita prompt.
The text was updated successfully, but these errors were encountered: