Repair pinned Qwen3 bundle with its original tokenizer - #49
Merged
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
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.
Problem and change
The pinned Qwen3-0.6B bundle mixes decoded SentencePiece tokens with literal byte-level BPE spellings for incomplete UTF-8 tokens. Original IDs
[9707, 0, 26525, 232]therefore produceHello!ĠðŁĺĬinstead ofHello! 😊. Encoding text back through the converted tokenizer can hide the defect by choosing different token IDs.Add an explicit, checksum-pinned artifact repair which replaces only this bundle's tokenizer section with the exact original Hugging Face tokenizer JSON. Existing v0.17.0-3 supports that section already. No runtime/output rewriting, token-ID remapping, automatic download changes, publication, or GPU gate changes.
Safety and validation
Hello! 😊; thinking/final and system/history recall pass. Original HF reference comparisons cover multilingual text, whitespace, normalization, literal BPE characters and split emoji IDs. C-string embedded-NUL limitation is explicitly excluded.c5c3f100affb7be6abe99bc2d00228ee3552bc6e0b8adb047b1b6eb3ffbe5e57.7026142f38b1eda1bd0a9357675e69742be23d4eagainstdd86d49, after fixing its source-header race finding. Zero remaining blocking findings.docs/qwen3_tokenizer_repair.md.Refs #48. The public original bundle/catalog remains unchanged; deployment/adoption is a separate step.
Additional desktop evidence
Hello! 😊.