Pin torchvision for gfp-gan #183
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
While i was testing an unrelated change (truss types), the gfp-gan truss started failing in CI examples. After retrying a few times, it looked it like it was an issue with the latest version of torchvision (AUTOMATIC1111/stable-diffusion-webui#13985).
Because we were not pinning torchvision, we were getting this later version, that does not seem to be compatible with gfp-gan.
The quick fix here is pinning torchvision, although I will acknowledge that this is not sustainable, at some point we will need to update gfp-gan library. This at least gets us back to passing CI.
Testing
Tested by deploying gfp-gan on staging, it worked successfully.