You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Qwen3.8-Flash-Next: transformers 5.16 drops \p{M} from the pre-tokenizer, so combining-mark text gets different ids #648
load_tokenizer (utils/hf.py) uses AutoTokenizer. With the pinned transformers 5.16.x, this checkpoint loads as Qwen2Tokenizer, which replaces the tokenizer.json pre-tokenizer with a split regex that lacks \p{M}. Text with combining marks then gets different ids than the model was trained on: नमस्ते दुनिया gives 10 ids instead of 6, and สวัสดีครับ gives 7 instead of 3. ASCII and precomposed Latin text are unaffected. It is the same on 5.15.1 and 5.17.0, and correct on 5.18.0+, which loads Qwen3_5Tokenizer.
Reproduced in the 1080 Ti deployment branch, rebuilt today on main 9c635a1 (torch 2.14.1+cu126, Triton 3.8, GTX 1080 Ti sm_61, Qwen3.8-Flash-Next-NVFP4 at 262K), which still resolves transformers 5.16.1: load_tokenizer returns Qwen2Tokenizer and gives 10 vs 6 ids for नमस्ते दुनिया and 7 vs 3 for สวัสดีครับ against tokenizer.json; café ✅ hello matches (4 vs 4).
Activity
gdevenyi commentedon Oct 13, 2026
Reproduced in the 1080 Ti deployment branch, rebuilt today on main 9c635a1 (torch 2.14.1+cu126, Triton 3.8, GTX 1080 Ti sm_61, Qwen3.8-Flash-Next-NVFP4 at 262K), which still resolves transformers 5.16.1:
load_tokenizerreturnsQwen2Tokenizerand gives 10 vs 6 ids forनमस्ते दुनियाand 7 vs 3 forสวัสดีครับagainsttokenizer.json;café ✅ hellomatches (4 vs 4).