fix: prevent UTF-8 fence scanner panics - #265
Merged
alecdotdev merged 1 commit intoJul 29, 2026
Merged
Conversation
PathGao
marked this pull request as ready for review
July 28, 2026 09:17
This was referenced Jul 29, 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
2 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.
Fixes #264.
The fenced-code scanner now reaches
trimmed[run_len..]only after confirming an ASCII fence marker, a matching opener, and a sufficient marker run. Ordinary multibyte content inside a fenced block can no longer be sliced at a non-character byte boundary.Adds a Rust regression test using Chinese-leading content inside a fenced code block, covering both no-panic behavior and continued processing after the closing fence.
Checks:
cargo test,npm test,npm run check.