NodeJS REPL first line strange behaviour

[ghost]

NodeJS 4.1.2, Windows 10 (x64), REPL:

C:\Users\admin\Desktop>node
> 1+1 // also ctrl+c, ctrl+d dont work here
1+1 // wtf?
2
> 1+1 // now works as intended
2

[silverwind]

Maybe a duplicate of #2996.

[silverwind]

Was able to reproduce in a VM and narrow it down a bit:

• Last good: 3.0.0
• First bad: 3.1.0

[silverwind]

Commit window: v3.0.0...v3.1.0. Nothing obvious there at least.

[Fishrock123]

Fwiw, crtl+d will not exit the repl if there are still characters on the line. (Side note: it should delete them instead, but it doesn't? Probably another bug. Edit it does, to the RIGHT: https://github.com/nodejs/node/blob/master/lib/readline.js#L701-L708)

@silverwind possible commits:

1738c96 (Net interacts with stdio)
1f12e03...455ec57 (buffers...)

[silverwind]

Looks like I was drunk when doing that regression window. Actual window is v2.3.4...v2.4.0. Suspecting bd01603, maybe 59f6b5d. cc: @rlidwka

[anseki]

This may be related to #2504.
This problem is existing since iojs-v2.3.2.

[silverwind]

#2504, like #2996 look to be caused by 8cee8f5.

My earlier regression test on this issue points to an issue present since 2.4.0.

[anseki]

@silverwind
I think so too.
v2.3.2, v4.2.1, etc. have issue #2504.
In v2.3.1-, no problem:

[silverwind]

Let's not confuse ourselves here. I'll try to bisect this (#3194) issue now.

[anseki]

Ok.
Of course I confirmed that the #3194 (i.e. strange in REPLE) is existing in v2.3.2.

[Fishrock123]

@silverwind any luck?

[silverwind]

The bug only seems to manifest on Windows 10, possibly 8, so no luck on my 7 machine. I'll have to set up a VM, it's going to take a while.

[Fishrock123]

hmm, maybe it's something related to our handling of stdin on those machines?.

[silverwind]

I'm positive this was fixed in af46112, seems I forgot to reference this issue.

[fatfisz]

Is there a chance of this landing in LTS any time soon? This is a bug, not a feature :)

[MylesBorins]

this will be landing with 4.2.4 this week

[fatfisz]

Good to hear that, thanks.

[fatfisz]

The exact same thing is happening in node 6 😢

[silverwind]

Yes, it regressed again in 5.7.0, the current issue is at #5384.