grandizzy

> (2) expect the current call context to revert. Hm, wouldn't the same confusion be happening with this one too?

> Ability to supply a flag to cast storage that forces the etherscan lookup, in case the local lookup returns weird results like the ones described above. This one's easy...

@wadealexc on a second thought - I used ``` cast storage 0x54945180dB7943c0ed0FEE7EdaB2Bd24620256bc --rpc-url $RPC_URL --etherscan-api-key $KEY ``` (which I see is used in https://github.com/Layr-Labs/eigenlayer-contracts too) and it is recognizing that...

@wadealexc ping in case you could answer above. thank you!

@QGarchery you can use `@tag` / `@rev` / `@branch` since https://github.com/foundry-rs/foundry/pull/9214 e.g. ``` forge install github.com/owner/repo@branch=my-branch forge install github.com/owner/repo@tag=v1.1 forge install github.com/owner/repo@rev=8e8128 ```

@QGarchery `forge install` follows now `foundry.lock` file, please reopen if this is still an issue. thank you!

Here's a sample on how reentrancy can be tested in invariants (adapted from https://github.com/rappie/echidna-rari-hack): https://github.com/grandizzy/foundry-rari-hack @mds1 do we need more of these or OK to close ticket for now and...

Yeah, had some testing for same scenario with `call_override` without any good results, there's more effort to put in to make it work. Agree, let's keep this one to make...

@MartinquaXD the releases to pin in CI for commits above are `nightly-54af8693b8fcc7a3f65136c1188e89661155955d` if this works OK please pin to `nightly-23191fbeccfcf901f7c28590cb962d9693373c21` and see if reproducible. thank you!

@MartinquaXD thank you, could you also please check `nightly-f0e24fb6cfc9018d986d3136ab00aa5077994994`. thank you!