[BUG] Fix convert_vae_pt_to_diffusers bug #11078
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
|
@bot /style |
|
Style fixes have been applied. View the workflow run here. |
lavinal712
changed the title
|
@sayakpaul @DN6 Please take a look at this PR when you have a chance. Thanks. |
hlky
approved these changes
Apr 8, 2025
|
Failing tests are unrelated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
I found that the
scripts/convert_vae_pt_to_diffusers.pyscript doesn't handle cases well where the encoder and decoder have attention, such as latent-diffusion/configs/autoencoder/autoencoder_kl_16x16x16.yaml at main · CompVis/latent-diffusion. Therefore, I made corresponding changes to support it.This PR is bug fix for #11077
@sayakpaul