Further flatten fuzzer fixes #523
Merged
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #523 +/- ##
==========================================
Coverage 100.00% 100.00%
==========================================
Files 83 83
Lines 14443 14588 +145
==========================================
+ Hits 14443 14588 +145 ☔ View full report in Codecov by Sentry. |
juntyr
force-pushed
the
further-flatten-fuzzer-fixes
branch
from
c9ea975
to
d5060c4
Compare
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
* [ ] I've included my change inCHANGELOG.mdThis PR is merged early to fix some long-time outstanding fuzzer-found issues. Most bugs are with serde (flattened fields in particular) and our fuzzer is adapted to not trigger them.
This PR should also improve one nasty edge case of parsing complexity.