Support cover images embedded in safetensors metadata#15319
Merged
AUTOMATIC1111 merged 1 commit intoAUTOMATIC1111:devfrom Mar 24, 2024
Merged
Support cover images embedded in safetensors metadata#15319AUTOMATIC1111 merged 1 commit intoAUTOMATIC1111:devfrom
AUTOMATIC1111 merged 1 commit intoAUTOMATIC1111:devfrom
Conversation
Owner
|
Can necessary information be included in the URL so that it's not needed to do this loop? ie page and item same as in |
ff1a326 to
c440250
Compare
Collaborator
Author
|
Thanks for the suggestion -- done. |
AUTOMATIC1111
approved these changes
Mar 24, 2024
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
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.
Description
Closes #15317
If an external preview image is not found, this will fallback to check if any cover image is embedded in the safetensors metadata, and if so, uses that within the UI instead.
Note that items already part of the disk cache won't initially be affected by this change, as the metadata read previously excluded this data.
Checklist: