You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SwarmUI's metadata updates directly modify the metadata record in the safetensors file, changing hash. Consider supporting AutoV3 hashes, which ignore the metadata record(s).
#115
Open
brendanhoar opened this issue
Jun 29, 2024
· 3 comments
SwarmUI (ex-StableSwarm) allows the user to update the metadata of model, but it stores the updates directly in the safetensors files. This breaks SHA256 and AutoV2 hashes, and for users who share models between applications, this may cause those users to lose the ability to pull new or updated metadata using your extension.
AutoV3 hashes, however, ignore the metadata and hash only the tensor information.
Civitai API's model hash endpoint has support for AutoV3 lookups, even though the official API docs don't include that yet.
Please consider adding support for the newer AutoV3 hash standard.
Thanks
B
The text was updated successfully, but these errors were encountered:
brendanhoar
changed the title
SwarmUI's metadata updates directly update the metadata record in the safetensors file. Consider supporting AutoV3 hashes, which ignore the metadata record(s).
SwarmUI's metadata updates directly modify the metadata record in the safetensors file, changing hash. Consider supporting AutoV3 hashes, which ignore the metadata record(s).
Jun 29, 2024
I'll look into it. I believe the hashing function I use can already skip hashing headers, I just need to pass a flag to the function and format for autov3.
On a side note, can we all just appreciate that Civitai's API documentation is eternally out of date and/or missing documentation entirely? I'm guessing autov3 support isn't actually that new.
Have you read document?
Yes.
Describe Issue
SwarmUI (ex-StableSwarm) allows the user to update the metadata of model, but it stores the updates directly in the safetensors files. This breaks SHA256 and AutoV2 hashes, and for users who share models between applications, this may cause those users to lose the ability to pull new or updated metadata using your extension.
AutoV3 hashes, however, ignore the metadata and hash only the tensor information.
Civitai API's model hash endpoint has support for AutoV3 lookups, even though the official API docs don't include that yet.
Please consider adding support for the newer AutoV3 hash standard.
Thanks
B
The text was updated successfully, but these errors were encountered: