-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yarn hangs at "Fetching Packgaes" on last package while installing Signal-Desktop #6246
Labels
Comments
ghost
assigned arcanis
Aug 8, 2018
ghost
added
the
triaged
label
Aug 8, 2018
Addendum: removing the explicit commit hash from the above dependency fixes the problem. It seems that this is a specific problem with the commit hash (on this package? There is no other package in the dependency list that has a commit hash.) |
same here:
|
Closing as fixed in v2 - the improved timeout and retry logic makes it a lot less susceptible to this kind of issues. |
paul-soporan
added
the
fixed-in-modern
This issue has been fixed / implemented in Yarn 2+.
label
Jan 3, 2021
also see #5055 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Bug report.
What is the current behavior?
Using this repository: https://github.com/signalapp/Signal-Desktop at tag
v1.14.4
sayingyarn install
runs fine, but at tagv1.15.0
(and above) the yarn process hangs indefinitely.If the current behavior is a bug, please provide the steps to reproduce.
Result is:
It hangs there. Since I'm assuming the folks at Signal actually test their builds, it seems to be a problem with my installation of yarn? Or maybe some particular combination of node/yarn/OS. It smells like a race condition 😕
Strace is here: https://gist.github.com/adimit/580a40e6c52bc4fb494e39e559ee983b
This is from the last status update, until I kill the process. It hangs indefinitely. I can also provide strace output from earlier in the execution, but the complete file is around 3MB.
Important: The offending package is
(from
package.json
.) If I delete that package (and only that package) the fetching packages step does run through (but actually building the application does not, obviously.)Please mention your node.js, yarn and operating system version.
There are related bugs in the tracker, but they all seemed to have a weird resolution to them. I don't have a VPN, I'm using the main NPM registry. If there's something I can tweak about my setup, please let me know.
The text was updated successfully, but these errors were encountered: