Node.js REPL hangs http requests on v0.12

[feyzo]

I found a problem with REPL on Node.js v12.0. It wasn't sending some of the http requests on time.

• Reproduced on OSX 10.10.2
• Didn't reproduce on openSUSE, Windows 7, Ubuntu 14.04

Here is the minimal reproducible example with documentation: https://github.com/feyzo/repl-hang-reduced-case
Also stackoverflow post: http://stackoverflow.com/questions/29076314/node-js-repl-hangs-http-requests

Problems:

1. http requests ran with repl interface hangs.
2. Running multiple repl requests after a failed one, hanged http requests stops hanging and reaches to server.

[jasnell]

Hmm.. Unable to replicate on 10.10.1. Planning to update to 10.10.2 tonight so will try it again.

[feyzo]

I started testing different versions after your comment @jasnell, it looks like problem started with 11.12 release.

Result breakdown:
✓: Working
-: Not tested
✖: Failing

• v0.11.0 ✓
• v0.11.1 -
• v0.11.2 -
• v0.11.3 -
• v0.11.4 -
• v0.11.5 -
• v0.11.6 -
• v0.11.7 -
• v0.11.8 -
• v0.11.9 -
• v0.11.10 ✓
• v0.11.11 ✓
• v0.11.12 ✖
• v0.11.13 ✖
• v0.11.14 -
• v0.11.15 -
• v0.11.16 ✖
• v0.12.0 ✖

[feyzo]

Git bisect result

First bad and installable commit:
e2fcfea

Had to skip these commits because make command was failing. Probably because these changes requires other set of commits to work:
d2f2a32
e92d35d

hey, authors @tjfontaine @saghul

[jasnell]

Hmm.. Oddly I'm still unable to replicate the issue. Let me play around
with it a bit more on a few different platforms to see what results I get.
On Mar 20, 2015 4:49 AM, "Feyzo" notifications@github.com wrote:

Git bisect result

First bad and installable commit:
e2fcfea
e2fcfea

Had to skip these commits because make command was failing. Probably
because these changes requires other set of commits to work:
d2f2a32
d2f2a32
e92d35d
e92d35d

hey, authors @tjfontaine https://github.com/tjfontaine @saghul
https://github.com/saghul

—
Reply to this email directly or view it on GitHub
#9420 (comment).

[feyzo]

@jasnell I was able to reproduce it on OSX 10.10.2 with two different machines.

Didn't reproduce on openSUSE, Windows 7, Ubuntu 14.04

[sixmen]

I think this is the same issue as #9310

[misterdjules]

Confirmed that this issue is a duplicate of #9310, and that it's fixed by #25475.