James
James
I'm still encountering this error as well, on all Arbitrum networks - One, Nova, and Goerli.
@zerosnacks seems to have been resolved by #7502
Interested in take a stab at this!
@PaulRBerg have you run into the scenario where you might want to toss-out multiple kinds of reverts for the same external call (while surfacing others)? Considering adding that functionality.
@PaulRBerg Sorry, to be more specific, I mean multiple kinds of errors with different data, to cover a set of anticipated & acceptable revert reasons that might arise from one...
@zerosnacks I have a (kinda janky) e2e [Gambit mutation test runner](https://github.com/emo-eth/gambit-runner) - when I wrote it, I had to explicitly disable dynamic test linking in a separate profile for Gambit...
I understand the reasoning for compiling without the optimizer – but I will note that this means currently any project that imports Seaport contracts directly cannot use forge coverage, as...