🐛 [Bug] Fix mistral tokenizer bug and related issues. #39
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
clownrat6
changed the title
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.
Because mistral update the tokenizer, some bugs occur when adopting previous
requirements.txt.Items
tokenizer bug: Error when loading tokenizer from a file: data did not match any variant of untagged enum ModelWrapper
updating
transformers==4.40.0 tokenizers==0.19.1can fix this bug.accelerate bug: TypeError: Accelerator.init() got an unexpected keyword argument 'use_seedable_sampler'
updating
accelerate==0.26.1can fix this bug.