fix(forge): isolate overloaded fuzz paths - #16307
Open
stevencartavia wants to merge 9 commits into
Open
Conversation
stevencartavia
requested review from
0xrusowsky,
DaniPopes,
figtracer,
grandizzy,
mablr and
mattsse
as code owners
August 21, 2026 04:55
Contributor
✅ Changelog foundThe deterministic check will validate the changed entry. |
mablr
previously approved these changes
Aug 21, 2026
mablr
left a comment
mablr
left a comment
Member
There was a problem hiding this comment.
SGTM code wise, do we need a benchmark ?
Member
Author
I don’t think so, this is a correctness fix outside the fuzzing hot loop. |
figtracer
reviewed
Aug 24, 2026
figtracer
reviewed
Aug 25, 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.
Uses selector-suffixed persistence paths for overloaded fuzz tests, preventing their failures, corpora, and showmap outputs from overwriting each other. Legacy failures remain replayable when their calldata selector matches the requested overload.