We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a known issue, that should be visible to the users.
Crytic-compile had breaking changes with 0.2.0
Until #2444 is merged, and we have a new Manticore's release, the installation through pip or github is broken for EVM.
As a temporary workaround: users can downgrade crytic-compile:
crytic-compile
$ pip install -Iv crytic-compile==0.1.13
If you use also Slither, I recommend to do this in a virtual environment, as downgrading crytic-compile will break Slither.
The text was updated successfully, but these errors were encountered:
The PR is merged, can we close this issue?
Sorry, something went wrong.
Hi @alexon1234, I think we can keep it open until the next release (#2456), for users' awareness
Closed w/ #2456
No branches or pull requests
This is a known issue, that should be visible to the users.
Crytic-compile had breaking changes with 0.2.0
Until #2444 is merged, and we have a new Manticore's release, the installation through pip or github is broken for EVM.
As a temporary workaround: users can downgrade
crytic-compile
:If you use also Slither, I recommend to do this in a virtual environment, as downgrading
crytic-compile
will break Slither.The text was updated successfully, but these errors were encountered: