grandizzy
grandizzy
@domob1812 I think this scenario should be solved with https://github.com/foundry-rs/foundry/issues/7931 and set `--block-time` to 0
@Rubilmax mind to open a ticket with a way to reproduce the problem you see? thank you!
@simon-something thank you, missed your comment. Could you create a PR in fcoundry, OK to close #6588 when we have it. Thank you!
@drortirosh in recent forge version there's `vm.mockFunction` cheatcode, would this help in your scenario? https://book.getfoundry.sh/cheatcodes/mock-function#description Thank you!
awesome, please close the ticket if you can use that one and no longer need a new cheatcode. Thank you!
> [b7f09d8](https://github.com/foundry-rs/foundry/commit/b7f09d836c55e12cf6c721bf2bdb789ab86c5843) operated under the assumption that the libafl function updated the history map, but it doesn't. So we either need to revert back to the other way or iterate...
added time based invariant campaigns in https://github.com/foundry-rs/foundry/pull/10190/commits/08e501aae466372947858d02dc2c9850d12d32e4 
@DaniPopes could you pls check addresses changes and if good to merge? Thank you
> Have we benchmarked this? It's still TBD, wanted to have it out for security researchers to start using it and provide feedback. If you strongly feel we shouldn't until...
> Well we're replacing the invariant runner by default with no fallback, I would at least check if we haven't had any regressions in performance and behavior Fair enough, for...