Bret

I'm also seeing it forking an ethereum archive node of mainnet. :/

I've taken a pcap, 100% of the RPC calls were responded to. There was one call that looked like it took 1 second to respond. ## Here is each request...

I'm not seeing any timeouts on the wire or from the server, of which I'm the only client using.

> @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...

Hi, I've captured the loopback device. I didn't see anything that took more than 0.5ms. I'll see what I can do about a reproducible scenario. 

hardhat v2.9.6 Specifically getting the following error: ``` HeadersTimeoutError: Headers Timeout Error at Timeout.onParserTimeout [as _onTimeout] (node_modules/undici/lib/client.js:1005:28) at listOnTimeout (node:internal/timers:561:11) at processTimers (node:internal/timers:502:7) ```

Same

I would like to see this merged as well. Going to use `https://www.npmjs.com/package/@brettdh/standard-version-expo` for now

@brettdh I get the following error when trying to run with the below configuration: ``` /Volumes/Development/Work/bretep/gate-code/.versionrc.js:34 updater: require.resolve('@brettdh/standard-version-expo/android/native/buildnum/code')(sdkVersion), ^ TypeError: require.resolve(...) is not a function at Object. (/Volumes/Development/Work/bretep/gate-code/.versionrc.js:34:100) at Module._compile...

I ended up just incrementing vs. using code: ```javascript module.exports = { bumpFiles: [ { filename: 'package.json', }, { filename: 'app.json', updater: require.resolve('@brettdh/standard-version-expo'), }, { filename: 'app.json', updater: require.resolve('@brettdh/standard-version-expo/android'), },...