Fix metadata template issue when using Adetailer #705
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
|
Thank you for this fix! The issue has been plaguing me for about a year now and driving me crazy!!!! I really hope the author will push out this change. THANK YOU! |
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.
This PR fixes a bug with how the prompt template is saved when using Adetailer: #703
I'm not sure why Adetailer does this, but after it processes an image, it calls the process() function of dynamic-prompts a second time and, during this second execution, dynamic-prompts overwrites its template metadata with a prompt value that no longer contains template information.
So this PR just makes sure not to overwrite the template metadata after it's written correctly the first time.