Draft
Conversation
AdamKorcz
force-pushed
the
add-json-encode-fuzzer
branch
from
0fe6cb6 to
d43769c
Compare
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.
Adds a structured fuzzer for the
_jsonC module's encoding paths (Modules/_json.c). The fuzzer constructs Python containers - int lists, string-keyed dicts, tuples, floats, and bare ints - from fuzzed input, then encodes them throughjson.dumps()under varied configurations. Separate branches exercise the default encoder,ensure_asciiin both modes,sort_keys, indented output with fuzzed indent levels, and a fully customJSONEncoderwith randomized separators andallow_nansettings. The goal is to cover the C-accelerated encoder's handling of diverse object graphs and option combinations..