-
Notifications
You must be signed in to change notification settings - Fork 792
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
[Bug]: DORA for Locon and LORA arent loadable "Version Mismatch" #635
Comments
#608 will solve this hopefully |
facing this issue as well with a kohya generated lora of mine... |
Was going to report an issue, but I think it's related to or the same as this one... However, I don't use DORA - I use almost exclusively IA3 due to its lightweight efficiency, and I cannot get most of them to work on Forge. I get the same error (LORA: Version Mismatch) and the IA3 (or sometimes other DyLoRA or LyCORIS) are not applied to the inference. I have some that do work though, so I am going to see what parameter are different on those that would be the culprit (will def check weigh decomp first)
^ If I put strikethrough in the third column that means I went back and tried to recreate an IA3 with the old settings from the functional IA3 in column 2 (did not produce a working version) |
IA3 is not supported in Forge, because it is also not supported in ComfyUI (the LoRA backend Forge uses). comfyanonymous/ComfyUI#1071 (comment) I'm not sure where comfyanonymous "officially" mentioned this. Probably Matrix or 4chan. If you look at the source it's clear no implementation exists though, unlike the webui. |
Hmm, thanks... So... that's weird that most of my 'older' ( like 1 month + ) IA3s do function as expected in Forge, but I can't recreate them with the existing parameters from Kohya on current version PS: Y'all are missing out! I appreciate the speed up in inference in Forge but it's not worth the trade for me. IA3 takes 15 minutes to train and weighs in at 1.2MB for SDXL finetune |
Checklist
What happened?
Kohaku LORA/LYCORIS modules loaded as LOKR or LOHA trained using dora decomposition method (dora_wd on lycoris) are able to be loaded, but if the module is a vanila LORA or LOCON (Which are treated by the same loader: locon come up with this error: error line
The primary difference dora is contributing is the addition of a decomposed weight parameter, it seems as though the lycoris module is being used to correctly load these for LOHA/LOKR but not being utilized for LOCON/LORA. I couldn't identify where the exact issue is.
Steps to reproduce the problem
I've uploaded an example model here to test https://huggingface.co/Blackroot/SD-DORA-Example-LORA/tree/main
This is a lycoris LORA trained using kohya-sd scripts with the following network parameters:
https://gist.github.com/CoffeeVampir3/dde66b3df88d32fa88f4d02d4bc0e901#file-dora_train2-sh-L93
Attempting to use this lora gives the aformentioned version error and does not apply the lora.
What should have happened?
The lora should be applied.
What browsers do you use to access the UI ?
No response
Sysinfo
sysinfo-2024-04-03-13-06.json
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: