Add fuzz seed for a long token followed by another token - #50
Merged
Conversation
bzick
force-pushed
the
fix/stream-token-longer-than-buffer
branch
from
July 24, 2026 09:20
ac28c81 to
19be587
Compare
bzick
changed the title
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
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.
While reviewing #43 I fuzzed the stream parser and hit an input (a 300-digit number followed by
A, buffer 100) that dropped the trailing token. Turned out to be the same bug as #44, which is already fixed on master — this input passes now.Just adding the seed to the corpus so this case stays covered. No code changes.