I’m running netlify dev on a gatsby project with functions setup.
Quite regularly (5-10mins) it crashes with the following error:
/Users/hannah/.nvm/versions/node/v10.15.1/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:600:12)
The error stops everything working, but doesn’t exit the process.
If this happens, or if I create an uncaught error, I’m also subsequently getting this:
Once this happens, the process does crash/exit. At this point, anything I type into the terminal doesn’t appear. So I have to close the window and open a new one.
Hi, @ErisDS, I’m not sure what would cause this. If you have time, would you be willing to please file an issue for this in our public repo for Netlify Dev here? Our developers are a bit more focused on conversations about Netlify Dev in GitHub than they are here in our community at the moment (limited resources and all that jazz).
Hey @pachiraDIG, welcome to Netlify Community. Thank you for brining this to our attention again. I’m looking into this issue actively but haven’t been able to reproduce it. Please follow up on it here: https://github.com/netlify/cli/issues/404
netlify-cli/node_modules/netlify-redirector/lib/redirects.js:116
throw ex;
^
Error: socket hang up
at connResetException (internal/errors.js:609:14)
at Socket.socketCloseListener (_http_client.js:398:25)
at Socket.emit (events.js:333:22)
at TCP.<anonymous> (net.js:668:12) {
code: 'ECONNRESET'
}
I’m going a little crazy how often netlify dev crashes.
@jarkin13 - I’m sorry you’re having to deal with frequent crashes, that’s annoying. Could you share a little more information? which version are you using? Is there a pattern to the crashes you are experiencing? is there anything that you have been able to do to mitigate?
Netlify Dev is still in beta, so there are some rough edges, that said, we are actively working to iron these things out - I’m happy to go check if we have an open issue if you give me a little more info. If there isn’t one, I’ll help you get one filed.
I’m regularly seeing the same error as jarkin13 developing a Gatsby site.
Could be coincidental but it often seems to happen when I’m resizing the browser window or going in/out of Chrome’s Dev Tools — wondering if it could be anything to do with responsive image requests?