Martin Magnus

When deriving `Deserialize` for API structs we ran into issues a few times because of this behavior. I understand that completely changing this behavior could be a serious breaking change...

Shortly after opening the issue I noticed that you already support named function arguments and return tuple fields so this is less of an issue for me now. But supporting...

`nightly-54af8693b8fcc7a3f65136c1188e89661155955d` and `nightly-23191fbeccfcf901f7c28590cb962d9693373c21` both did not reproduce the error.

`nightly-f0e24fb6cfc9018d986d3136ab00aa5077994994` reproduced the issue, although it's not the culprit since the release right before (`nightly-bfb1cb6b118b7e07a1de0fdea64a6cf44eb3a174`) already had the problem.

Not sure if this makes sense but the first release that consistently fails is [this](https://github.com/foundry-rs/foundry/releases/tag/nightly-e2a22506797d05e64808302a14f2292fe163ba35). It only only bumps a minor version of a dependency, though. The 2 versions with...

Yeah, can check the releases between, too. > do you happen to use wss rpc urls or https only? Only http.

We are using self hosted nodes on OVH as the `--fork-url`. For mainnet we are using `reth` and for gnosis chain `erigon` in case that matters.

Still looks like 03-19 is the culprit. All the 03-18 builds are working.

The latest nightly still has the issue. This is a [run](https://github.com/cowprotocol/services/actions/runs/14913926020/job/41894773973?pr=3379) which has the issue. To see the logs from `anvil` search for `line=`. This is a successful [run](https://github.com/cowprotocol/services/actions/runs/14914027834/job/41895108330?pr=3379) with...

> I can't confirm if https://github.com/foundry-rs/foundry/pull/10471 fixes this behaviour but ... Will rerun the tests when the fix hits nightly and will let you know. Thanks for jumping on this...