-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
train_dreambooth_lora_flux validation RuntimeError: Input type (float) and bias type (c10::BFloat16) should be the same #9476
Comments
Even the below leads to OOM
|
Had the same issue. As a temporary fix, I added the code to convert the latent to bfloat16 on line 762 of pipeline_flux.py and it worked. But this was just temporary, and I don't know if it was the correct thing to do or not |
Uncomment this line and comment the one below; that resolved the issue for me |
@sayakpaul do you recall why we have this line commented in
|
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
Not sure if this problem is totally resolved, I was trying to use
but got error and black images similar to #9549
Then I tried the PR fix in #9565 but still have the error
The code I run:
|
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
Describe the bug
When train_dreambooth_lora_flux attempts to generate images during validation,
RuntimeError: Input type (float) and bias type (c10::BFloat16) should be the same
is thrownReproduction
Just follow the steps from
README_flux.md
for DreamBooth LoRA with text-encoder training:System Info
Diffusers:
Accelerate config:
Who can help?
@sayakpaul @linoytsaban
The text was updated successfully, but these errors were encountered: