F. Eugene Aumson

Thank you for using Hardhat. If there is a problem in Hardhat, we will need to be able to reproduce it before we can fix it. Please provide more information....

Thanks for following up. It's important that we get a _minimal_ reproducible example, not one in a large repo. Sometimes it's acceptable to use a large repo to simply verify...

Fixed via #2218

Thank you for using Hardhat. In general, if there is a problem in Hardhat, we will need a minimal reproducible example in order to investigate it. See https://stackoverflow.com/help/minimal-reproducible-example Can you...

Closing for lack of response. Feel free to re-open if you'd like to continue to pursue this. Thanks again for using Hardhat.

This issue has been added to our internal backlog, meaning that we intend to work on it, but that it has not yet been scheduled.

No one is working on it yet. Feel free to dive in. However, please be aware that the initial work will be "product work" rather than "technical work," which means...

Thank you for using Hardhat. Can you provide a more complete reproduction scenario? Perhaps in a separate repo or in an attachment? Something I can easily just run. Thanks.

I'm closing this because it sounds like Hardhat is behaving as expected. This error message is simply the result of a network timeout, and the mere presence of this message...

@bretep thank you for this. I've re-opened the issue. Clearly this isn't necessarily an issue connecting to the remote node. In particular, the presence of `HardhatNode.mineBlock()` in the call stack,...