-
Notifications
You must be signed in to change notification settings - Fork 10.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete SHA256SUMS for now #416
Conversation
Delete this for now to avoid confusion since it contains some wrong checksums from the old tokenizer format Re-add after #374 is resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that it's best not to confuse people with wrong checksums
it would have been better to only delete the |
I wasn't sure if all of them were wrong/old or just some. In any case better to take it out for now until it's fully updated and checked first, right? |
afaik most where correct, @gjmulder ? |
@Green-Sky they were "correct" in that they reflected the *.pth data files I have and I was waiting for people to confirm that everything was correct before merging, but @prusnak decided to go ahead with what I had generated. |
This was a mistake. There was no need to erase all hashes, we could have kept original file hashes (PTH). Please leave more time for review than just 3 hours. |
I apologize for the premature merge. Shall I restore the pth hashes? |
* Revert "Delete SHA256SUMS for now (#416)" This reverts commit 8eea5ae. * Remove ggml files until they can be verified * Remove alpaca json * Add also model/tokenizer.model to SHA256SUMS + update README --------- Co-authored-by: Pavol Rusnak <[email protected]>
Delete this for now to avoid confusion since it contains some wrong checksums from the old tokenizer format
Re-add after #374 is resolved