Immediate ENOTCONN error in Windows 7

[ShimShamSam]

Everytime I start nodemon I get the following error:

Error: read ENOTCONN
at errnoException (net.js:884:11)
at Socket._read (net.js:389:21)
at Socket.Readable.read (_stream_readable.js:320:10)
at Socket.read (net.js:291:43)
at new Socket (net.js:185:10)
at process.stdin (node.js:660:19)
at Object. (C:\Users<User>\AppData\Roaming\npm\node_modules\nodemon\nodemon.js:819:8)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)

OS: Windows 7
Node: 0.10.7 (Windows)

It may be pertinent to note I use Cygwin for my console.
Nodemon continues to run and work perfectly despite the error and the error only shows up when I first run it. Restarts caused by file changes do not trigger the error.

[t2n]

same here,

29 May 07:21:16 - [nodemon] v0.7.8
Error: read ENOTCONN
at errnoException (net.js:884:11)
at Socket._read (net.js:389:21)
at Socket.Readable.read (_stream_readable.js:320:10)
at Socket.read (net.js:291:43)
at new Socket (net.js:185:10)
at process.stdin (node.js:660:19)
at Object. (C:\Users\user\AppData\Roaming\npm\node_mules\nodemon\nodemon.js:819:8)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
29 May 07:21:16 - [nodemon] to restart at any time, enter rs
29 May 07:21:16 - [nodemon] watching: C:\project_directory
29 May 07:21:16 - [nodemon] exception in nodemon killing node
29 May 07:21:16 - [nodemon] starting node server.js

node 0.10.7 (Win)

[JamesKyburz]

Don't think it's to do with nodemon but readline on cygwin.

I am running node 10.0.4 on windows 7 with cygwin and get the following instead of a node prompt
➜ winify node

events.js:72
throw er; // Unhandled 'error' event
^
Error: read ENOTCONN
at errnoException (net.js:883:11)
at Socket._read (net.js:389:21)
at Socket.Readable.read (_stream_readable.js:294:10)
at Socket.read (net.js:291:43)
at new Socket (net.js:185:10)
at process.stdin (node.js:660:19)
at startup (node.js:145:16)
at node.js:901:3

[jordwalke]

Any resolution here?

[remy]

Not yet - I'd appreciate if anyone else that has win7 to hand if they're
able to debug the situation?

On 29 June 2013 12:42, Jordan W notifications@github.com wrote:

Any resolution here?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/176#issuecomment-20228548
.

[ShimShamSam]

Switching from Cygwin to msysgit solved this issue and a multitude of others.

[stale]

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3