[Web] Bump web-tokenizer to 0.1.6 #67
Merged
Conversation
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
|
Fixes mlc-ai/web-llm#675 (comment), where the error is like this for newly compiled MLC models on WebLLM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR bumps web-tokenizer to 0.1.6 to reflect the latest HEAD changes.
Without bumping this, WebLLM would run into RUST-related error (
thread '<unnamed>' panicked at src/lib.rs:26:50:), likely due to the newly compiled weights and tokenizer files in mlc-ai's HF repo are not matching with theweb-tokenizerpackage.Unrelatedly, we also upstream
package-lock.json