zerosnacks

> > To avoid visual regression, applied a change to style warning message content in yellow and error message content in red. > > This is not right, only the...

From https://github.com/foundry-rs/foundry/issues/4440#issue-1601444539 The debugger should be interactive to allow for collapsing traces, show/hiding more information, etc. Tenderly debugger/trace [UX](https://twitter.com/TenderlyApp/status/1623679228884447234) is very nice IMO so is a good source of inspiration....

From #5553: - Making it smarter about where solidity structs are laid out and labelling them with variable names - visual storage/memory explorer with struct/variable knowledge - calling convention/ABI.encode awareness...

@jistro are you launching Anvil with any special commands or flags? Would you mind trying with `--block-time 1`? Are the contracts you are deploying very large (>24kb)?

Thanks @DaniPopes! Moving this to `foundry-rs/book` as the actionable item is related to the documentation and confirmed to not be a bug

Thanks for your bug report, I'm able to reproduce the bug with this setup: https://gist.github.com/zerosnacks/9c4651967d7836620a961a81a9731d92

I wonder if the suggested change of defaulting to the default signer address deviates from the `eth_call` specification that defines the `from` field as optional: https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_call and clients usually defaulting...

Related: https://github.com/summa-tx/coins/issues/139, this still uses 0.8 in `alloy-signer-local`

https://github.com/summa-tx/coins/pull/140 was merged, unfortunately still appears to be blocked on `k256` as noted above. Foundry's migration away from 0.8 is also blocked on this.

Related: https://github.com/foundry-rs/foundry/issues/1078