Program panics when running with --fork-network flag

[franciszekjob]

Describe the bug (observed vs expected behavior)

Program panics when running with --fork-network flag:

Forking from block: number=563201, hash=0x19389df5c082f83dbd159be0538cc48252db2c803f3519f5a440e0b6a1bab89
thread 'main' panicked at /Users/franciszekjob/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/blocking/shutdown.rs:51:21:
Cannot drop a runtime in a context where blocking is not allowed. This happens when a runtime is dropped from within an asynchronous context.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2025-03-02T22:49:44.048269Z ERROR reqwest::blocking::client: Failed to communicate successful startup: Ok(())

To Reproduce
Steps to reproduce the behavior:

1. Run starknet-devnet --fork-network https://rpc.pathfinder.equilibrium.co/testnet-sepolia/rpc/v0_8

Devnet version

• I am using Devnet version: built from branch starknet-0.13.4
• This happens with a dockerized Devnet (check the box if true).
• This does not appear on the following Devnet version: v0.2.0-rc.1

System specifications

• OS: mac

[FabijanC]

This has been observed with Devnet run in debug mode (i.e. non-release mode): #530

How did you install Devnet?

[franciszekjob]

This has been observed with Devnet run in debug mode (i.e. non-release mode): #530

Right, it's not present in release mode.

How did you install Devnet?

In fact I just run it in debug mode, so it's duplicate of the issue above.

Thanks for quick response guys!