Implications of "lora key not loaded"

[tildebyte]

I occasionally see this https://github.com/comfyanonymous/ComfyUI/blob/90aa59709985ffa1b02b6330b7720ed399fbf4df/comfy/sd.py#L159 when testing LoRAs from bmaltais' Kohya's GUI (too afraid to try running the scripts directly). I don't get any errors or weird outputs from the GUI or scripts during training (and this doesn't happen with every LoRA), so I have literally no way to predict which LoRAs will do this.

I don't know what it is telling me (I mean, I'm a Python coder by trade, so I know what the words mean :laughing:) - I don't understand the implications.

• Is this even important?
• Does it affect the model's function or performance?
• (Most importantly) If the above is true, is there a fix?
• If there isn't a fix, do you have any insights into what training parameter(s)/failure(s) cause this?

P.S. I can't really characterize the performance of a model with this message - I'm still new to this... I guess my observation would be that the CLIP side of the model seems weak :shrug:, but then none of the LoRAs I've trained so far have worked particularly well (even those without this message) :rofl:

[tildebyte]

Probably should've mentioned that all such keys are named like "lora_te1_text_model_encoder_layers"

Full log attached lora_keys_not_loaded.txt

[comfyanonymous]

Yes those warnings are important it means that the keys with those names were not loaded.

Those loras should be working so make sure you are updated to the latest ComfyUI. If it still gives those warnings give me your workflow and lora and I'll look at it.

[tildebyte]

Thanks for the quick reply

Can't distribute the LoRA :(

OTOH, I twiddled some training parameters and "resumed" training (not that there really is such a thing in the GUI, but...), and so far, my first checkpoint after 500 steps does not complain.

It's definitely a legitimate complaint from Comfy - I obviously had a bad setting in there previously

P.S. Likewise for step 1500 checkpoint just tested