-
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
Unable to compile foundry master in projects that depend on foundry crates #3179
Comments
do you also have a revm dependency? |
I do have an revm dependency too yes. I'm not quite sure what you mean by bumping ethers, ethers is resolved to the latest master commit. To reproduce the issue one create a new project and add for example
|
Sorry I copied the wrong traceback. Will update it. |
what's your rust version? |
I'm not using rustup. But as I mentioned just before I copied the wrong traceback into the issue. It should be fixed now. |
iirc revm requires at least 1.64 |
The https://github.com/bluealloy/revm/runs/8284537901?check_suite_focus=true#step:3:13 I get the same compilation errors if I run |
does it work with 1.64? |
I get the same errors with |
this turned out to be an issue where we haven't bumped breaking changes from ethers-rs yet, you can patch ethers-rs until #3183 lands |
Thanks @mattsse Patching doesn't work for me as I mentioned in the original issue post. I'm not in urgent need of a fix though, so no problem! |
Component
Anvil
Have you ensured that all of these are up to date?
What version of Foundry are you on?
No response
What command(s) is the bug in?
No response
Operating System
Linux
Describe the bug
Foundry currently relies on the
Cargo.lock
file to pin ethers to gakonst/ethers-rs@91d8c21.Crates that use foundry as a dependency will have the ethers dependencies of foundry crates resolve to the latest version that is incompatible since gakonst/ethers-rs#1682 was merged:
If one patches ethers to gakonst/ethers-rs@91d8c21 compiling
foundry-evm
fails withThe text was updated successfully, but these errors were encountered: