Yarn: Yarn install is stuck for no reason on v0.17.8

[tristanbes]

Possible Bug

What is the current behavior?
Yarn (0.17.8) is getting stuck at "Fetching packages..." [1074/1075].
I deploy my application to 2 exact same servers (same versions of everything). One server has this problem, one has not.
I fixed the problem by removing .yarn-cache and .yarn-config

If the current behavior is a bug, please provide the steps to reproduce.
Run yarn install and watch it getting stuck before finishing. Since I deleted the cache, there's no way I reproduce it for you, sorry guys. My report sucks.

What is the expected behavior?
yarn install finishes without problems

Please mention your node.js, yarn and operating system version.
Node v6.2.1
Linux Debian Jessie

[torifat]

@tristanbes Seriously, one software engineer to another. If I assign this issue to you. How will you go about it?

[tristanbes]

Like really really sad. If that helps you, I really wondered myself if I should opened it "as is".

But I choose to report it anyway to log this on internet if other users will encounter this and have more information to share.

Or maybe "my" fix will help them.

[tristanbes]

PS: Even if you close this issue because it does not contains enough information, this still can help others and I won't get mad about it. // cc @torifat

[torifat]

@tristanbes I'm not closing it right away. Just wanted to know your thought process 😄

[bestander]

0.17.9 has --verbose flag, you can now see which download gets stuck.
This looks like a network issue, and could be resolved with a retry.
@tristanbes, how many times did you try and got this problem before fixing it with clearing caches?

[tristanbes]

It was 2/3 times as far as I recall

Envoyé de mon iPhone

Le 27 nov. 2016 à 05:03, Konstantin Raev [e-mail] a écrit :

0.17.9 has --verbose flag, you can now see which download gets stuck.
This looks like a network issue, and could be resolved with a retry.
@tristanbes, how many times did you try and got this problem before fixing it with clearing caches?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[bestander]

@tristanbes, 2/3 times as 66% of all times or just 2 or 3 times?
Can you repro this with --verbose flag?

[tristanbes]

@bestander : (just 2,3 times until we manually clear the cache) It didn't occured again to us since this report. If it happens to us again, we'll use the verbose flag to post a better bug report ;-)

Thanks.

[bestander]

Thanks, let's close this one and open a new one if it happens again