'socket hang up' error thrown randomly

[revett]

- Do you want to request a feature or report a bug?

Bug

- What is the current behavior?

At points during development the following error occurs which stops the entire Netlify Dev stack:

.../node_modules/netlify-redirector/lib/redirects.js:116
      throw ex;
      ^

Error: socket hang up
    at createHangUpError (_http_client.js:323:15)
    at Socket.socketCloseListener (_http_client.js:364:25)
    at Socket.emit (events.js:194:15)
    at TCP._handle.close (net.js:600:12)

Looks like it was also reported on the community forum back in April - https://community.netlify.com/t/netlify-dev-regularly-crashes/551

- If the current behavior is a bug, please provide the steps to reproduce.

I haven't been able see any common pattern for what causes this.

- What is the expected behavior?

Should not crash.

- Please mention your node.js, and operating system version.

• Node: v10.15.1
• Using yarn
• Netlify CLI 2.12.0

[akramsaouri]

Been happening to me too.
I'm using CRAL with graphql-yoga, any updates?

[dustb0wl]

+1 - I've had the same issue

[pushred]

For me this occurs when I change a function:

◈ functions/guests/guests.js modified, reloading...
/Users/example/.nvm/versions/node/v10.15.3/lib/node_modules/netlify-cli/node_modules/netlify-redirector/lib/redirects.js:116
      throw ex;
      ^

Error: socket hang up
    at createHangUpError (_http_client.js:323:15)
    at Socket.socketCloseListener (_http_client.js:364:25)
    at Socket.emit (events.js:194:15)
    at TCP._handle.close (net.js:597:12)

...or a CRA src file:

Compiling...
Compiled successfully!
/Users/example/.nvm/versions/node/v10.15.3/lib/node_modules/netlify-cli/node_modules/netlify-redirector/lib/redirects.js:116
      throw ex;
      ^

Error: socket hang up
    at createHangUpError (_http_client.js:323:15)
    at Socket.socketCloseListener (_http_client.js:364:25)
    at Socket.emit (events.js:194:15)
    at TCP._handle.close (net.js:597:12)

Version: netlify-cli/2.13.0 darwin-x64 node-v10.15.3

It's also worth noting that with CRA at least it's processes remain running after the crash and must be killed before netlify dev can start again.

99970 ttys000    0:00.14 /Users/example/.nvm/versions/node/v10.15.3/bin/node /Users/example/dev/node_modules/.bin/react-scripts start
99971 ttys000    0:12.25 /Users/example/.nvm/versions/node/v10.15.3/bin/node /Users/example/dev/node_modules/react-scripts/scripts/start.js

[zslabs]

Adding onto what @pushred mentioned above; it'd be great if the port could also be shut-down in the event an error is caught - re-googling sudo lsof -i tcp:3000 and kill -QUIT <PID> is sadly something I will never memorize and is the bane of my existence.

[DomVinyard]

yes, I'm getting this repeatedly, every edit almost

[leibovic]

This has been happening to me as well. It looks like netlify-redirector isn't open source, so it isn't even possible to try to debug the root of the issue.

[nonissue]

Yah, I'm getting this as well. For anyone on mac, if you don't have any other node processes running, killall node saves me from having to use lsof. Use it with caution though obviously.

The issue seems like an unhandled error isn't been returned properly somewhere, but I haven't been able to specifically isolate when it happens.

[samblacklock]

Also seeing this all the time, both on build and on file changes. We invested quite a bit of time into refactoring our frontend to run completely on netlify dev so this is really frustrating! We are running an Ember.js app with a bunch of netlify functions

One thing we have noticed is that using Chrome in particular triggers this error where other browsers don't seem to...

[brendan1212]

I'm actually getting the error almost constantly using Firefox, so its not just a Chrome issue.
I can't seem to narrow down the cause.

May I ask why this hasn't been given attention since August?

[brendan1212]

@RaeesBhatti @sw-yx

[RaeesBhatti]

This is high on my priority list but I haven't able to reproduce it because it is not consistent. It would be greatly helpful if you can share any of your repos that have this issue more often. I've tried this on macOS, is it more common on other OS'es?
Also, in the meantime, we pushed a change recently that cleans up the CRA-like server processes when the Netlify Dev crashes. Please provide feedback on that issue here: #580

[dustb0wl]

@RaeesBhatti For what it's worth, I was getting it consistently and frequently in Jekyll projects on MacOS, even when it was freshly generated. I haven't used it in a few months, but I can try and reproduce again. Did not seem to be browser specific in my experience.