You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My thoughts are that sometimes hardhat takes longer than expected(especially given that I'm 300ms away from alchemy) to start listening on port 8545 and connection refused error is not handled anywhere. Some experiments shows that if we catch the error here things work fine.
The text was updated successfully, but these errors were encountered:
Environment information
ape
and plugin versions:Linux sajal-thinkpad 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
What went wrong?
When using hardhat in forking mode (eth mainnet) with following config
and following test case
with following command
WEB3_ETHEREUM_MAINNET_ALCHEMY_API_KEY="REMOVED" ape test --network :mainnet-fork:hardhat -v DEBUG tests/test_Fork.py
The result is random.
How can it be fixed?
My thoughts are that sometimes hardhat takes longer than expected(especially given that I'm 300ms away from alchemy) to start listening on port 8545 and connection refused error is not handled anywhere. Some experiments shows that if we catch the error here things work fine.
The text was updated successfully, but these errors were encountered: