Closed blmalone closed 2 months ago
This is due to https://github.com/foundry-rs/foundry/pull/7358.
On v1.1.0
build_info = true
in foundry.toml
, which disables caching and forces compilation. Whereas, on v1.3.0
the build_info
flag is removed from foundry.toml
, thus enabling the cache.
I think the solution here is what we discussed with @klkvr in the past—instead of disabling cache, the build info flag should generate a new build-info on each compiler run, and we link artifacts to their corresponding build info, like hardhat does.
@yash-atreya do you expect this issue to be worked on anytime soon?
we've improved build-info tracking and enabled cache for runs with --build-info
flag, so this should be resolved I believe https://github.com/foundry-rs/foundry/pull/8164
Following up on this, @blmalone could you check if you are still running into issues? If not we can mark this as resolved
@zerosnacks I tried to test this to confirm it's working but it seems another bug has been introduced: https://github.com/foundry-rs/foundry/issues/8555
For reference, related PR for #8555 : https://github.com/foundry-rs/foundry/pull/8560
Going to mark this as resolved as I'm not seeing the same behavior anymore.
Component
Forge
Have you ensured that all of these are up to date?
What version of Foundry are you on?
What command(s) is the bug in?
Operating System
macOS (Apple Silicon)
Describe the bug
Steps to reproduce
I've noticed two cases of unexpected behavior.
op-contracts/v1.1.0
op-contracts/v1.3.0
andop-contracts/v1.1.0