EINVAL errors (events.js:160) with Node 7.1.0 on Windows 10

[mischah]

• Version: 7.1.0
• Platform: Windows 10
• Subsystem: Events

Hej there,

several users have problems with different packages running node 7.1.0 on Windows 10:

• write EINVAL "Unhandled 'error' event" on Windows 10 with Node 7.1.0 mochajs/mocha#2577
• Not able to run on Node v7.1.0 on Windows react/react-native#10824
• npm install electron appears to fail with error EINVAL electron/electron#7919
• Error running yo with Node.js 7.1 on windows 10 (Error: write EINVAL) yeoman/yo#485
• CLI doesn't work with Node v7.1.0 yeoman/yo#486

All of them seem to have the following in common:

• It used to work with node 7.0.0 and stopped working with 7.1.0
• A similiar error with different stacktrace:

events.js:160
      throw er; // Unhandled 'error' event

Error: write EINVAL

Could you enlighten us? Is it a regression in Node.js?

Thanks, Michael

[bnoordhuis]

It's possible the libuv upgrade introduced a regression, I don't see anything else that is an obvious culprit. What happens when you revert commit 106d719?

[killroy42]

For me it broke between 7.0.0 and 7.1.0 spawning webpack-dev-server in a child process. Related: #9534

[mischah]

What happens when you revert commit 106d719?

I can’t reproduce the errors right now (wrong OS).

But if someone else can, how could they check if this helps?
Am I right with the following steps?

1. Clone nodejs/node
2. Checkout branch v7.1.0-proposal
3. Revert commit 106d719
4. Build node source for Windows
   • See: https://github.com/nodejs/node/blob/master/BUILDING.md#windows
5. Try to reproduce the error

[skcc75]

We have the same problem in Windows 10 x64

[EdwinChua]

I'm new to React Native, and have encountered the same problem. Just did a fresh install, and downloaded the Awesome Project (Android), following the instructions on https://facebook.github.io/react-native/docs/getting-started.html

I'm running Windows 10, x64

Error message
C:\Users\Edwin\AwesomeProject>react-native run-android
events.js:160
throw er; // Unhandled 'error' event
^

Error: write EINVAL
at exports._errnoException (util.js:1022:11)
at WriteStream.Socket._writeGeneric (net.js:715:26)
at WriteStream.Socket._write (net.js:734:8)
at doWrite (_stream_writable.js:334:12)
at writeOrBuffer (_stream_writable.js:320:5)
at WriteStream.Writable.write (_stream_writable.js:247:11)
at WriteStream.Socket.write (net.js:661:40)
at WriteStream.stream.write (C:\Users\Edwin\AwesomeProject\node_modules\ansi\lib\newlines.js:36:21)
at Object.execFileSync (child_process.js:506:20)
at Object.run (C:/Users/Edwin/AwesomeProject/node_modules/react-native/local-cli/cliEntry.js:157:16)

[skcc75]

@bnoordhuis @mischah Rolling back 106d719 solves the problem for us with webpack-dev-server. Also solves the problem with mocha mochajs/mocha#2577

[felixrieseberg]

npm-windows-upgrade here, we have the same issue.

[skcc75]

Here is our Win10 x64 build of Node.js master (7.1.1-pre) sans 106d719 to test:

• 7z of Release folder: (link deleted) (69.8MB)
• 7z of node.exe: (link deleted) (4.2MB)

P.S. See #9542 (comment) for updated build and link

[killroy42]

I tried your test build, and while I didn't rebuild all my binaries and thus cannot run all my services with it, it does start up webpack-dev-server without issue and appears to run.

[bnoordhuis]

Can someone try this patch? libuv/libuv#889 is currently my prime suspect, seeing how all the bug reports are for Windows 10.

diff --git a/deps/uv/src/win/tty.c b/deps/uv/src/win/tty.c
index 18d68d0..88b8ef9 100644
--- a/deps/uv/src/win/tty.c
+++ b/deps/uv/src/win/tty.c
@@ -134,7 +134,7 @@ typedef enum {
   UV_UNSUPPORTED
 } uv_vtermstate_t;
 /* Determine whether or not ANSI support is enabled. */
-static uv_vtermstate_t uv__vterm_state = UV_UNCHECKED;
+static uv_vtermstate_t uv__vterm_state = UV_UNSUPPORTED;
 static void uv__determine_vterm_state(HANDLE handle);

 void uv_console_init() {

cc @nodejs/platform-windows

[seishun]

@bnoordhuis
Fixes mocha for me.

[killroy42]

I also had issues with weird color in my console, such as black text on black background. Makes sense as your patch is referencing ANSI support.