bug (anvil): thread 'fork-backend-thread' panicked at 'A Tokio 1.x context was found, but timers are disabled.

[mds1]

Component

Anvil

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

anvil 0.1.0 (76b00d0 2022-05-28T00:08:43.25713Z)

What command(s) is the bug in?

anvil --fork-url $OPTIMISM_RPC_URL

Operating System

macOS (Intel)

Describe the bug

I'll start anvil against an Optimism RPC URL (which may not be relevant to the bug, but it's how I'm currently using anvil to access contracts deployed on that network). Often, after running a deploy script against it a handful of times, anvil crashes with the below error. The preceding RPC methods vary and are not always the same as the sequence shown below.

eth_getTransactionCount
eth_getCode
thread 'fork-backend-thread' panicked at 'A Tokio 1.x context was found, but timers are disabled. Call `enable_time` on the runtime builder to enable timers.', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.18.0/src/time/driver/handle.rs:58:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[1]    90513 abort      anvil --fork-url $OPTIMISM_RPC_URL

[mattsse]

potentially fixed one commit later #1750

should be in latest nightly

[mds1]

Ah so I actually ran foundryup -b master about an hour ago and am using commit 562d876. It seems anvil --version doesn't take that into account

[mattsse]

that's odd, because these constants are generated during build.

is this still an issue on nightly?

[mds1]

Updated again this morning, and so far this hasn't happened when using anvil to test some scripts over the last hour, so this appears to be resolved. Going to close for now and will re-open if it occurs again