fix(cheatcodes): fix interval notation in memory error#14126
Merged
mattsse merged 2 commits intofoundry-rs:masterfrom Apr 4, 2026
Merged
fix(cheatcodes): fix interval notation in memory error#14126mattsse merged 2 commits intofoundry-rs:masterfrom
mattsse merged 2 commits intofoundry-rs:masterfrom
Conversation
zeroprooff
requested review from
0xrusowsky,
DaniPopes,
grandizzy,
mattsse,
onbjerg and
zerosnacks
as code owners
mattsse
approved these changes
Apr 4, 2026
Member
mattsse
left a comment
mattsse
left a comment
There was a problem hiding this comment.
Updated the CLI golden output to match the corrected safe-memory interval notation. Focused verification: cargo test -p forge --test cli failure_assertions::mem_safety_test_should_fail -- --exact --nocapture
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.
Fix incorrect interval notation in
disallowed_mem_writeerror message. Rust'sRange<u64>is[start, end)(start included, end excluded), but the message showed(start, end](opposite).Before:
safe range: (0x00, 0x20]After:
safe range: [0x00, 0x20)