Assume LFS OID is SHA256 value if SHA256 field missing from LFS Info. #61
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 fix allows models that have been updated in their repo to be detected as hash mismatch and re-downloaded.
The Hugging face api does not have a field 'SHA' or 'SHA256' on LFS files. The LFS oid is the SHA256 hash of the file so use that when the LFS SHA256 is missing, which it always will be.
Api example: https://huggingface.co/api/models/Qwen/Qwen3-0.6B/tree/main