grandizzy
grandizzy
> @grandizzy how can a natspec-only change impact the push bytes? @cruzdanilo so actually it is different, for example for contract ``` contract MyTest { function dummy() external {} }...
yeah, would be nice to have such, going to look into updating function to ignore metadata then https://github.com/foundry-rs/foundry/blob/44d98ea9359070017819ba44f3d11e4fedb63420/crates/evm/fuzz/src/strategies/state.rs#L322-L355
@cruzdanilo btw, if you find acceptable as an workaround until a fix is implemented - you could use `forge snapshot --no-metadata` for such
@DaniPopes please take a look when you have time, would love to get this merged and take feedback from community. Thank you 🙏
> > > By the way this is caught by the fuzzer now. should probably close this Awesome! Do you have the test handy to share, would love to have...
thank you! confirm it is caught with fuzzer default settings :tada:
related https://github.com/foundry-rs/foundry/issues/8614
@mjpowersjr @cstoneham can't you use `evm_snapshot` / `evm_revert` instead `anvil_reset` for your scenarios?
indeed, this does not happen with newer eth_account python library (tested with 0.13.14), but confirmed it does with the one used in brownie ```python >>> from eth_account import Account, messages...
#5407 looks related to this too