-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
got an unexpected keyword argument 'num_decay_steps' #2812
Comments
Well I rolled back to 63c1e48 and it worked again, so yeah |
Was this in the sd3-flud.1 branch? SDXL does not work in that branch at the moment. |
Yeah it was, seems like it, the latest it was working for me was that commit |
It is still not working on current commit: d24fae1 |
Can you share the .json config for the training? I can't reproduce the issue. It might be related to a particular parameter you use |
Attached |
I have the same issue and it stemmed from kohya's sd-scripts repository. I can form this happens when trying to trani a FLUX dev1 LoRA. I can provide a toml-config if useful. The issue is when I set the scheduler to cosine or linear. The issue goes away if I set constant instead. I believe it could be this change causing the problem: |
@bmaltais the latest commit fixed the problem! Prodigy with Cosine is working! |
I pushed the fix. Should be good to go. |
I'm sorry if this is an issue that has been opened before, but this morning when I was just going to train a new lora I got this, I'm using Prodigy and Cosine, not cosine with warmup? Also just yesterday it was working perfectly, I'm on the sd3-flux.1 branch, when I just updated to the new commit because the white color was giving me aneurysms, I started getting this, even when I go back to the previous commit I still get it.
The text was updated successfully, but these errors were encountered: