-
Notifications
You must be signed in to change notification settings - Fork 81
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: anvil-zksync able to start even if the port is busy #542
Conversation
host, | ||
config.port, | ||
err | ||
); |
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.
Hmm, I don't think this is a good fallback. If I were running a tool in CI and saw this behaviour I would have been unpleasantly surprised.
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.
Hm, indeed. I though for a second that anvil
does that -- but no:
anvil
Error: Address already in use (os error 98)
Location:
/home/runner/work/foundry/foundry/crates/anvil/src/lib.rs:229:28
I guess we have to replace the fallback with just error propagation.
* refactor: reduce usage of `ForkStorage` outside `inner` module (#539) * reduce usage of `ForkStorage` outside `inner` module * adapt for zkos * fix destination path (#541) * fix: anvil-zksync able to start even if the port is busy (#542) * fix: closes #512 - start instance even if port is busy * chore: apply make lint:fix * chore: refactor test to make use of anvil-zksync instance * chore: remove no longer needed deps * chore: remove no longer needed deps * chore: bump actions/upload-artifact: v3 to v4 due to CI fail * chore: bump actions/upload-artifact / download: v3 to v4 due to CI fail * compilation fixes --------- Co-authored-by: Daniyar Itegulov <ditegulov@gmail.com> Co-authored-by: Nisheeth Barthwal <nbaztec@gmail.com> Co-authored-by: Dustin Brickwood <dustinbrickwood204@gmail.com>
What 💻
Why ✋
Evidence 📷