-
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 install hangs during "Fetching packages..." #764
Comments
I have the same issue on Windows 10 using nodejs v6.2.0 x64. It hangs when fetching the last package:
|
@sorgloomer yep same behaviour, it is indeed hanging on last package. |
Same issue but with bower.json. In this case it's working on my local macOS. (with a complication #846) {
"name": "jaguar",
"version": "0.0.0",
"private": true,
"dependencies": {
"bootstrap": "~3.3.5",
"devicejs": "2ae5c775e35ccc837589e5af34e292c54936778c",
"jquery": "2.1.3",
"jquery-transform": "e195b9a7118558bb1141e50b80380ea5f31dffb8",
"moment": "2.14.1",
"moment-timezone": "0.5.5",
"owl-carousel2": "2.0.0-beta.2.4",
"raven-js": "3.5.1",
"ua-parser-js": "0.7.10",
"underscore": "1.8.3",
"object-fit": "~0.4.2",
"picturefill": "^3.0.2",
"jquery-selectBox": "316c77f157cb25c7a6ea36822143ac9d97845067"
},
"resolutions": {
"jquery": "2.1.3"
}
} Every build on CircleCI that does |
Same issue here.
|
Same issue here |
It works on Windows 10 with |
I thought the whole point was to exclude the npm client from the equation |
Updating to nodejs v6.7.0 solved my issue |
Broken on node v4, working on v6.7 |
hangs on:
|
My jenkins machine was also seeing the same hang-on-final-package-install, with:
Upgrading to node 6.8.1 via |
Confirmed. Hangs on 6.1.0 and upgrading to 6.8.1 fixed it. |
(Same here - Node 6.2 -> 6.8 fixes it) |
Failing for me on CircleCI:
Of particular note, it consistently hangs on some file being pulled from a private git repository. The file varies, but it's always that repository. This command shows the file descriptors opened by a given process:
I filed a related issue here on CircleCI forums with other info, probably not more significantly valuable than what is here. Update: Updating to Node v6.9.1 resolves the issue on repeated rebuilds with and without cache. |
So, to wrap up some data here in a bow for a troubleshooter: |
This seems to happen to me as well. |
so do i, sucks |
Same issue here |
Same: OSX: 10.11.6 Works with node > 6.7 |
Hangs for me as well at 1040/1041 |
I just ran into this. Node 7.4.0 |
Datapoint: I've had this hung for 2 days now. The process wasn't doing anything useful: https://gist.github.com/benlangfeld/24f704753d1564d2db102f972d066008 |
I figured my issue out, but it might be specific to only a few people. I'm on windows 10 vanilla-masker was included to be downloaded by yarn, but vanilla-masker is incompatible with windows due to a poorly named directory. I changed the dependency to use lagden-vanilla-masker (https://www.npmjs.com/package/lagden-vanilla-masker), a copy of vanilla-masker which renamed the offending directory to be windows compatible. |
My issue turned out to be a disk full condition. |
What worked for me was getting off VPN: before:
after:
|
**Summary** Fixes #764. Turns out when fetching packages from remote sources via Git, it may ask for a username or password and get stuck there since we run it in the background. This patch passes the following env variables to disable any prompts: 1. `$GIT_ASKPASS=""` This is the command Git runs to get username and pass. Setting it to an empty string disables it and git exits with an error. 2. `$GIT_TERMINAL_PROMPT=0` This is new in Git 2.3 and it prevents git from even trying to ask for a password. Surpasses `$GIT_ASKPASS` above. 3. `$GIT_SSH_COMMAND="ssh -oBatchMode=yes" This is also new in Git 2.3 and it makes git make the call to ssh via this command. `BatchMode=yes` option tells ssh to not do anything interactive (because batch/script mode) like password prompts in case publickey auth fails etc. **Test plan** Do `yarn add git+https://github.com/Napsty/privrepo.git#1.0.2`. `yarn` hangs before this patch and fails with a "Refusing to download" error after the patch.
**Summary** Fixes #764. Turns out when fetching packages from remote sources via Git, it may ask for a username or password and get stuck there since we run it in the background. This patch passes the following env variables to disable any prompts: 1. `$GIT_ASKPASS=""` This is the command Git runs to get username and pass. Setting it to an empty string disables it and git exits with an error. 2. `$GIT_TERMINAL_PROMPT=0` This is new in Git 2.3 and it prevents git from even trying to ask for a password. Surpasses `$GIT_ASKPASS` above. 3. `$GIT_SSH_COMMAND="ssh -oBatchMode=yes"` This is also new in Git 2.3 and it makes git make the call to ssh via this command. `BatchMode=yes` option tells ssh to not do anything interactive (because batch/script mode) like password prompts in case publickey auth fails etc. **Test plan** Do `yarn add git+https://github.com/Napsty/privrepo.git#1.0.2`. `yarn` hangs before this patch and fails with a "Refusing to download" error after the patch.
Had the same issue. Deleting the |
i try
it works for me |
I had the issue with |
this is happening in large packages. it can be nice if a warning is given on a certain size. |
I had the same issue. I believe it is version conflict with node. My project was using v81.2. I simply switched to the correct version and yarn stoped hanging: |
Still have this problem in v1.9.4, but same as #5055 |
Had the same problem: Looks like it was probably a corrupted yarn.lock file. Doing the following fixed it:
|
Same issue OS: OSX 10.14.1 (Mojave) |
I solved it by switching to different network (hotspot). I guess our office network firewall had some restrictions. |
Same issue OS Windows 10 My solve: update motherboard drivers |
Had the same problem: I solved it by doing the following: than again tried the install command and it works. though it takes few minutes to complete the process so be patient it will work. In my case it took 10 minutes (Depends on the internet speed) to complete the process. |
Updating yarn did not help. In my case one of the packages was too large and couldn't download before the timeout Solution is to install using or add .yarnrc file to your project and put this inside: |
same here:
|
Same problem! [email protected] Executed for this repo: Windows 10 |
Long story short, check your vpn. Is it connected? A coworker and I were debugging this same issue. It would just stop at a specific package although we weren't sure which package. Basically, the person had restarted their computer earlier and when they started it back up, they also had to setup a new password for their vpn. So their vpn never automatically reconnected. Since it was an "issue with yarn", I didn't think much about the vpn. But we have a company repo with a few packages and that is where it was hanging. :/ |
Weirdy, this worked |
My download was getting stuck on the last dependency. None of the answers above helped / gave any clue. I switched to a mobile hotspot and it worked |
Thank You 👌👌 |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
yarn install hangs at fetching packages and does not provide any further information as to the cause.
If the current behavior is a bug, please provide the steps to reproduce.
With the following package.json run the below
What is the expected behavior?
Installation should succeed.
Please mention your node.js, yarn and operating system version.
The text was updated successfully, but these errors were encountered: