Skip to content

refactor(bindings): read deployed forwarders over HTTP instead of forking#86

Open
jonaprieto wants to merge 1 commit into
nextfrom
refactor/bindings-tests-http-provider
Open

refactor(bindings): read deployed forwarders over HTTP instead of forking#86
jonaprieto wants to merge 1 commit into
nextfrom
refactor/bindings-tests-http-provider

Conversation

@jonaprieto

@jonaprieto jonaprieto commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

The bindings tests spun up a forked anvil per chain just to read view functions. Anvil only reports ready after it fetches fork state from the RPC, so a slow or rate-limited RPC blows past anvil's 10s startup timeout and the test panics with Timeout (and it degrades as chains are added).

This reads the deployed forwarders with a plain HTTP provider and deploys the reference forwarder once on a local non-forked anvil to get the expected version constant, so no test forks a chain anymore. Same fix already merged in generic-call-forwarder #26.

@jonaprieto jonaprieto self-assigned this Jul 2, 2026
…king

The bindings tests spun up a forked anvil node per chain just to read view
functions (protocol adapter, logic ref, version). Anvil only reports ready
once it has fetched fork state from the RPC; over a slow or rate-limited RPC
that exceeds anvil's 10s startup timeout and the test panics with `Timeout`.
It also gets slower and more fragile as more chains are added.

Read the deployed forwarders with a plain HTTP provider, and deploy the
reference forwarder once on a local (non-forked) anvil to obtain the expected
version constant. No test forks a chain anymore.
@jonaprieto jonaprieto force-pushed the refactor/bindings-tests-http-provider branch from 21c6e1b to 6b0a3dc Compare July 2, 2026 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant