Fix markdown generation crash on LLM special tokens#4154
Merged
Conversation
The gpt-tokenizer encode() call rejects special tokens like <|im_start|> that appear in documentation code examples. Pass allowedSpecial: 'all' since these are content, not control tokens.
ArvinJ-H
approved these changes
May 28, 2026
metricjs
approved these changes
May 28, 2026
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
3 participants
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.
Summary
gpt-tokenizerencode()call inscripts/generate-markdown.mjsthrows when it encounters LLM special tokens (<|im_start|>,<|im_end|>) that appear in documentation code examples (specifically the Ollama Modelfile template in the on-premises providers page).{ allowedSpecial: 'all' }to treat these as regular content rather than disallowed control tokens.Context
This is blocking the deploy workflow after the DOC-3498 on-premises docs merge to
tinymce/8.Test plan
encode(content, { allowedSpecial: 'all' })handles the problematic tokens without error