-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: handle duplicate forkids #5939
fix: handle duplicate forkids #5939
Conversation
The expected behavior is that |
this is rather a bug how me map the assigned uint256 forkids internally, because both forking off the same endpoint at the same height, so we need to change how we keep track of those, will fix shortly |
@mattsse ping |
@DaniPopes whoops, totally forgot about this. I took a page out of the cargo playbook and used an URL hack to make them unique, this was easier than rewriting the internal mappings... |
crates/forge/tests/it/repros.rs
Outdated
@@ -198,3 +198,6 @@ test_repro!(6180); | |||
|
|||
// https://github.com/foundry-rs/foundry/issues/6437 | |||
test_repro!(6437); | |||
|
|||
// <https://github.com/foundry-rs/foundry/issues/5935> | |||
test_repro!(5935); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
order :)
Closes #5935
we have an edge case with forkids internally that can lead to an out of bounds bug if the same URL is used twice and the local mapping is updated
https://github.com/foundry-rs/foundry/blob/master/crates/evm/src/executor/backend/mod.rs#L1624-L1634