Matt Solomon
Matt Solomon
From my testing, trying to flesh out depth vs. runs relationship a bit: - Default fuzz settings do not catch it, regardless of number of runs (I only tried up...
Awesome, created https://github.com/foundry-rs/foundry/issues/7848 to track and will close this one
I think adding the scientific notation output was a breaking change? I don't remember that always being there. If so, that does break cast integrations and usage in scripts. I...
Also seeing this issue, cc @mattsse, same cause and fix described by @thedavidmeister above A more complex repro can be found [here](https://github.com/ethereum-optimism/superchain-ops/pull/34/files), notice the empty contracts added in `DeployConfig.s.sol` and...
> do we want to expose a new config for the number of threads to run tests or just document that it can be changed by using `RAYON_NUM_THREADS` env var?...
How can I reproduce? I cloned your repo on that branch, tried `forge build --force --extra-output evm.bytecode.opcodes` and `forge build --evm-version paris --force --extra-output evm.bytecode.opcodes`, but in both cases no...
Could turn off metdata with `bytecode_hash = 'none'`, that way you preserve the solc version which is controlled by the CBOR metadata
Per chain compiler config related to https://github.com/foundry-rs/foundry/issues/7720. It proposes a UX for different profiles per contract, probably would need to be tweaked for this purpose
This is great! > (for example if the persisted sequence fails in 100 steps but config was altered to run with a depth of 50 then persisted sequence will pass)...
> Yes, that's correct, there'll only be first 50 runs resulting in test pass. That was done to avoid situations like the one described here https://github.com/crytic/echidna/issues/1231 where changes in configs...