-
Notifications
You must be signed in to change notification settings - Fork 4
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
Error saving merged models: "KeyError: "sd_merge_recipe" #8
Comments
thanks for your reporting, A merged model by Model mixer always sets the metadata, I guess you have tried to save is not a valid merge, fixed by commit 5fc7a42 |
I'm still having issues with saving a working model. I always get an error when "Safetensors" is toggled so I untoggle that to have it save a CKPT. Those saved files are broken/don't work though. Here's what the model toolkit extension shows for the one I just tried to save w/ Model Mixer: The error I get trying to save when Safetensors is toggled is:
I've also run into this error complaining "'NoneType' object has no attribute 'lowvram'", but I don't recall the order to which that came up. I saw it yesterday also. I'm running A1111 on a very high end workstation w/ 64gb RAM and a 4090 (if that matters).
|
same issue here, this is another issue. |
fixed! #11 will be merged shortly. |
Played around with it for the last couple of hours and seems to be working great now. Good job! |
#18 |
The save current merge model feature hasn't yet worked for me. In earlier versions I'd end up w/ a checkpoint that would come up as mostly "junk" data when loaded into the "model toolkit" extension. I checked them there as they were odd sizes and did not work in the app or for training. Those files would be generated if I unticked "Safetensors". Leaving that ticked gave a different error and failed to generate a checkpoint (sorry I don't have a log of that).
At the moment though when I try to save a model that has been created in an open session I'm getting the error "KeyError: 'sd_merge_recipe'":
The text was updated successfully, but these errors were encountered: