Open ChiHaoLu opened 5 months ago
@ChiHaoLu hi, thanks for the report! could this be a change or regression in Foundry? can you check which forge --version
you have working locally and failing on your workflow?
I'm seeing the same thing as well as of a couple days ago. No problems running slither locally, just in the action
@ChiHaoLu hi, thanks for the report! could this be a change or regression in Foundry? can you check which
forge --version
you have working locally and failing on your workflow?
forge 0.2.0 (e0ea59c 2024-04-24T00:17:37.065879000Z)
This is my foundry version. And everything works in locally.
BTW, the CI will work when ignore-compile=false
, which means compiling by the slither-actions itself.
So far we suspect this might be caused by https://github.com/foundry-rs/foundry/issues/7878
If you have the option, installing an older Foundry release seems to work around the problem: foundryup -v nightly-f625d0fa7c51e65b4bf1e8f7931cd1c6e2e285e9
Unfortunately for those using the automatic compilation (i.e. no ignore-compile
) , the action always installs the latest nightly build of foundry, but we're thinking of adding an option to pin Foundry to a specific release: #85
The foundry issue has been resolved upstream and the latest nightly build includes the fix, can you retest your workflows and let us know if this is now working?
It works! Thanks a lot!
The slither-actions worked successfully in few days ago, but today it suddenly appears the cannot find file error.
In the local test it works successfully, and I cannot figure out why this error will occur even the compile successful.
My github workflow is:
The result is:
In my lib, the
openzeppelin-contracts/contracts/access/Ownable.sol
is existed.And here is my
slither.config.json
, the remapping part is same withfoundry.toml
: