Fix inpaint node #3284
Merged
Fix inpaint node #3284
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
Seems like this is the only change needed for the existing inpaint node to work.
Kyle0654
approved these changes
May 1, 2023
Contributor
Kyle0654
left a comment
Kyle0654
left a comment
There was a problem hiding this comment.
Approving this as a temporary fix, though we do intend to remove all of these nodes in favor of the latents nodes (and using subgraphs to represent more complex processes).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Seems like this is the only change needed for the existing inpaint code to work as a node. Kyle said on Discord that inpaint shouldn't be a node, so feel free to just reject this if this code is going to be gone soon.