EHOSTDOWN not handled for http.request in 7.10.0

[albert-olive]

• Version: v7.10.0
• Platform: 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64

Hi,

In our package.json we have added to the script test the --runInBand flag in order to speed up travis tests. We're 5 people in our team and all of them have no problems but I'm having this error every time I run the script. This is what's looks like:

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

Error: connect EHOSTDOWN 169.254.169.254:80 - Local (192.168.8.46:63717)
    at Object.exports._errnoException (util.js:1050:11)
    at exports._exceptionWithHostPort (util.js:1073:20)
    at internalConnect (net.js:889:16)
    at lookupAndConnect (net.js:977:5)
    at Socket.realConnect (net.js:945:5)
    at Agent.connect [as createConnection] (net.js:77:22)
    at Agent.createSocket (_http_agent.js:195:26)
    at Agent.addRequest (_http_agent.js:157:10)
    at new ClientRequest (_http_client.js:212:16)
    at Object.request (http.js:26:10) 

The script:

"test": "export APP_ENV=development && jest --no-cache --runInBand --forceExit",

If I remove this flag, I don't get this error. I don't know if it's related to Jest, Node, Travis, etc but I have been looking to resolve it for a long time and I have no more ideas.

My version are:

• Node: v7.10.0

• Jest: v19.0.2

• OS: macOS Sierra 10.12.4

Thanks in advance.

[evanlucas]

Does this only happen on v7.10.0?

[albert-olive]

Yes, I'm only at v7.10.0. The others are at v6.10.3, v7.5.0, v7.2.0 and v7.5.0

[evanlucas]

Thanks! We are aware of this issue and a fix is being worked on. Closing as this is a duplicate of #12841. Be on the lookout for the next v7.x release (which will probably be next week). Thanks!

[vingrad]

+1

[bnoordhuis]

@vingrad Don't do that, posting context-free "+1" comments. You end up spamming a ton of people.

[EduardoDeMagalhaes]

Hi Is the issue solved? I'm still having it... Version 0.4.28

[dreamloud-zz]

Also having this issue

[seet61]

Also having this issue
node v8.9.0
the issue solved?

[hathamneh]

Also having this issue :(

[bnoordhuis]

It was fixed a long time ago so you're probably not experiencing the same issue. Please open a new issue and include steps to reproduce.

[ezequielmuxito]

Hi, guys! I'm in trouble.

I installed: npm install gulp-sass --save-dev
but when I type the command: gulp sass it presents this error I have already read many things.
[18:53:19] Starting 'sass' ...

events.js: 183
throw er; // Unhandled 'error' event
^
Error: Gem sass is not installed.

these are the codes so gulpfile.js

var gulp = require ('gulp');
var sass = require ('gulp-ruby-sass');

// task for sass
gulp.task ('sass', function () {
return sass ('sass / * .sass'). pipe (gulp.dest ('css'));

});

[mmarchini]

According to this Error: Gem sass is not installed you need to install Ruby Sass (http://sass-lang.com/install). Doesn't seem to be a Node core problem, you'll probably get better help in nodejs/help or StackOverflow.

[rsmodake]

Hi All,

I have installed protractor on my machine. When I fire below command,
webdriver-manager update
I get below error,

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

Error: tunneling socket could not be established, statusCode=407
at ClientRequest.onConnect (/usr/local/lib/node_modules/protractor/node_modules/tunnel-agent/index.js:166:19)
at Object.onceWrapper (events.js:293:19)
at emitThree (events.js:116:13)
at ClientRequest.emit (events.js:197:7)
at Socket.socketOnData (_http_client.js:443:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at readableAddChunk (_stream_readable.js:178:18)
at Socket.Readable.push (_stream_readable.js:136:10)
at TCP.onread (net.js:561:20)

I am using node version V7.10.0

Please help me to resolve the issue. My colleague is having same version, but he is not facing any issues.

[jonathangaldino]

I'm still having this issue with node v8.9.4

[chillyistkult]

Same issue for me.

[MadanBhandari]

If someone find an solution, please share. Same issue with V9.2.0

[apapirovski]

This error just indicates that there's an error event that's unhandled somewhere in the application or its dependencies. It's extremely unlikely (actually, impossible) that anyone here is having the exact same issue as OP. Check the error message and follow the dependency chain to figure out what exact issue you're having. If you believe it's actually in Node.js core then open a new issue and provide as much info as possible.

[apapirovski]

I've updated the title of this issue to be more descriptive in order to avoid the unrelated Google traffic flowing to this issue.

[nujey]

I'm still having this issue with node v8.11.3