POSTs whose bodys are instances of createReadStream hang with latest node about got HOT 5 OPEN

For old node

{"foo":"bar"}
complete

Process finished with exit code 0

for node 20.11.1

Process finished with exit code 13

from got.

Does it work without Nock? If yes, then the issue is definitely Nock as it should work with anything that normally works without it.

You can replace Nock with https://httpbin.org for testing.

from got.

Yes, it works without nock, replacing it with https://httpbin.org/post, but similarly nock works with axios in place of got.

from got.

@sindresorhus I tend to agree that it might be an issue with Got, in particular with asPromise(request), which returns promise that never resolves in some rare conditions (changes to streams that were done in node v20.10.0 + some nock behavior).

from got.

FYI patching Nock source the following way resolved the issue for me:

index d82c2446b540759cbc54ad7b26222a80109b8ec9..bf24add845d12e436c97b3ea5e2e38f87b77d489 100644
--- a/lib/intercepted_request_router.js
+++ b/lib/intercepted_request_router.js
@@ -68,7 +68,7 @@ class InterceptedRequestRouter {
     // For parity with Node, it's important the socket event is emitted before we begin playback.
     // This flag is set when playback is triggered if we haven't yet gotten the
     // socket event to indicate that playback should start as soon as it comes in.
-    this.readyToStartPlaybackOnSocketEvent = false
+    this.readyToStartPlaybackOnSocketEvent = true

     this.attachToReq()

from got.