Doesn't work well on a flaky connection

[appsforartists]

Do you want to request a feature or report a bug?
Not sure.

What is the current behavior?
I'm at an airport today, so I've been tethering on my phone and using in-flight WiFi. Every time I try to run yarn, I eventually get a socket hang up error on an arbitrary package. Presumably, it doesn't handle mobile connectivity very well. npm install works in these same scenarios.

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

What is the expected behavior?

• Be able to install a particular module without worrying about the rest of the installed modules.
• Retry requests if one times out.

Please mention your node.js, yarn and operating system version.
yarn v0.15.1
node v6.2.1
macOS v10.11.6

[Daniel15]

Somewhat similar to #627, in that we're not retrying in a case where we probably should.

[designorant]

Interesting. I often work while traveling through areas with little or no coverage, and found using NPM almost impossible then. Yarn seemed very promising, and some quick tests showed it does behave just fine having most/all packages cached, but it does appear equally ineffective when starting from scratch indeed. It would be great if it was more proactive on flaky networks.

---

Context:

I currently work on a project with 803 packages in total.

On a 1mbps, 0% packets drop rate, 5ms delay connection, the install times with cleaned caches are as follows:

• npm install => 8m 0s
• yarn => 3m 38s

On a 1mbps, 10% packets drop rate, 500ms delay connection, the rather unscientific results are as follows:

• npm install just hangs without any feedback at some point.
• yarn trips up either with a socket hang up error, or just hangs.

--verbose was of no use in both cases.

[th3fallen]

can confirm yarn will trip up on a slow/unstable connection with socket hung up regardless of what you do

[deepu105]

I'm facing the same as well. On windows with a tethered mobile connection (not very fast but npm works)

yarn install v0.15.1
info No lockfile found.
[1/4] Resolving packages...
error https://registry.yarnpkg.com/progress: socket hang up
    at createHangUpError (_http_client.js:206:15)
    at TLSSocket.socketOnEnd (_http_client.js:298:23)
    at emitNone (events.js:85:20)
    at TLSSocket.emit (events.js:179:7)
    at endReadableNT (_stream_readable.js:906:12)
    at nextTickCallbackWith2Args (node.js:474:9)
    at process._tickCallback (node.js:388:17)
info Visit http://yarnpkg.com/en/docs/cli/install for documentation about this command.

[juangl]

Same in Archlinux with my 1mbp connection. npm i works.

[gitnik]

This happens to me despite having a very stable connection

[jromero2k]

Windows 10, 512kbps... I can't finish any install. Lots of (random) socket hang ups. NPM works properly most of the time

Example:

yarn add v0.15.1
info No lockfile found.
[1/4] Resolving packages...
error https://registry.yarnpkg.com/babel-preset-es2015-node: socket hang up
at createHangUpError (_http_client.js:252:15)
at TLSSocket.socketOnEnd (_http_client.js:344:23)
at emitNone (events.js:91:20)
at TLSSocket.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)

[wx-chevalier]

i run into the same problem,in MacOS 10.11.5, node 5.3.0, npm 3.9.5:

 yarn add material-ui
yarn add v0.15.1
info No lockfile found.
warning webpack-react-redux-boilerplate@1.0.2: "dependencies" has dependency "react-komposer" with range "^1.11.0" that collides with a dependency in "devDependencies" of the same name with version "^1.13.1"
[1/4] 🔍  Resolving packages...
error socket hang up
    at TLSSocket.onHangUp (_tls_wrap.js:1090:19)
    at TLSSocket.g (events.js:261:16)
    at emitNone (events.js:73:20)
    at TLSSocket.emit (events.js:167:7)
    at endReadableNT (_stream_readable.js:906:12)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
info Visit http://yarnpkg.com/en/docs/cli/add for documentation about this command.

[stanonyime]

Having the same issues on Windows 8, yarn 0.15.1, third-world connectivity ( flaky networks). npm works fine

[henri-hulski]

Here exactly the same on Debian Jessie with mobile connection (EDGE about 12kbps).

[henri-hulski]

If I try yarn upgrade I get something like this:

yarn upgrade v0.15.1
[1/4] Resolving packages...
error socket hang up
    at TLSSocket.onHangUp (_tls_wrap.js:1097:19)
    at TLSSocket.g (events.js:273:16)
    at emitNone (events.js:85:20)
    at TLSSocket.emit (events.js:179:7)
    at endReadableNT (_stream_readable.js:913:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
info Visit http://yarnpkg.com/en/docs/cli/upgrade for documentation about this command.

No chance to get it working.

npm works fine.

[hustcer]

yarn v0.16.0
node v6.9.1
macOS v10.12

warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
...

however, npm works well.