Skip to content
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

Fibers/Node-Gyp Hanging on yarn install #3041

Closed
dheerajbhaskar opened this issue Apr 4, 2017 · 14 comments
Closed

Fibers/Node-Gyp Hanging on yarn install #3041

dheerajbhaskar opened this issue Apr 4, 2017 · 14 comments

Comments

@dheerajbhaskar
Copy link

Do you want to request a feature or report a bug?

Bug

What is the current behavior?
Hangs on node-gyp or fibers task

image

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

  1. New project
  2. Yarn add chimp

What is the expected behavior?
That it adds chimp successfully in reasonable time

Please mention your node.js, yarn and operating system version.
node v7.8.0
yarn v0.22.0 (reproducible on latest stable v0.21.3 also)

Reference:
Reference:
http://stackoverflow.com/questions/42862378/fibers-node-gyp-hanging-on-yarn-install

@codingwaysarg
Copy link

codingwaysarg commented Apr 4, 2017

Same issue here using npm

image

@codingwaysarg
Copy link

Related?

nodejs/node-gyp#1165

@ghost ghost mentioned this issue May 4, 2017
@dheerajbhaskar
Copy link
Author

Wow! I was trying to file an issue because I encountered this issue and found my own issue that I'd filed earlier.

Is more info required to fix this?
Here's a package.json to reproduce this:

{
  "name": "test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "chimp": "^0.48.0"
  }
}

@dmr
Copy link

dmr commented Jun 27, 2017

@dheerajbhaskar did you solve the problem? Same issue here...

@marvinhagemeister
Copy link

Just tried it on my machine and it installs fine with the package.json posted above

OS: MacOS Sierra
node 8.1.2
yarn 0.24.6

@dheerajbhaskar
Copy link
Author

@marvinhagemeister this is am issue on windows.

@dmr nope, just using npm for now. Was too much trouble using yarn. Also npm now has lock file feature now and is faster than before I think

@dmr
Copy link

dmr commented Jun 28, 2017

My problem was solved by removing node_modules, uninstalling node, reinstalling everything.

@dheerajbhaskar
Copy link
Author

Thanks for the update @dmr

I think I'm going to sit this one out. This way too many hoops to be worth it. I can just do npm installand be done with it.

I've reported the bug because I care for the project

@WillsonHaw
Copy link

This is also an issue on our CI servers, using Node 8.1.4, Npm 5.2.0, yarn 0.27.5
We've had to roll back to node v6.3.1 and npm 3.9.5 to get it working again as a workaround...

@theandrewlane
Copy link
Contributor

theandrewlane commented Jul 14, 2017

I'm running into the same issue on Node 8.1.4 and Yarn 0.27.5 on Win 7 Enterprise. Following @dmr's recommendation, hopefully that resolves the node fibers/gyp issue.

UPDATE: Uninstalled Yarn & Node, removed /node-modules, node cache, and yarn cache. Reinstalled Node 8.1.4 and Yarn 0.28.1. No issues.

@kittaakos
Copy link

Same problem here on a Win10 VirtualBox. It works on OS X. Also, no issues when using npm on Windows.

Steps to reproduce:

mkdir foo && cd foo && yarn init -y && yarn add fibers && yarn

Full output:

kittaakos@DESKTOP-531EDFN MINGW64 ~/Desktop
$ npm --version && node --version && yarn --version && python --version
4.2.0
v7.9.0
0.27.5
Python 2.7.11

kittaakos@DESKTOP-531EDFN MINGW64 ~/Desktop
$ mkdir foo && cd foo && yarn init -y && yarn add fibers && yarn
yarn init v0.27.5
warning The yes flag has been set. This will automatically answer yes to all questions which may have security implications.
success Saved package.json
Done in 0.08s.
yarn add v0.27.5
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
[1/1] ⠂ fibers: gyp info spawn args   '-Goutput_dir=.' ]

Does anyone know what could be the root of the problem? I could try to look into it if someone could give me pointers. Thanks in advance!

@kittaakos
Copy link

I have wiped yarn, and installed it (v0.27.5) via choco (it comes with Node.js v8.2.1
and npm 5.3.0). After that, I was able to use yarn to install fibers.

kittaakos@DESKTOP-531EDFN MINGW64 ~/Desktop
$ mkdir baz && cd baz && yarn init -y && yarn add fibers && yarn
yarn init v0.27.5
warning The yes flag has been set. This will automatically answer yes to all questions which may have security implications.
success Saved package.json
Done in 0.14s.
yarn add v0.27.5
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 1 new dependency.
└─ fibers@2.0.0
Done in 4.73s.
yarn install v0.27.5
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.39s.

@AlexandreBonneau
Copy link

yarn still fails to install fibers/node-gyp when using the latest stable node v9.10.1.

To fix that, you need to temporarily downgrade node to v6.11.5 using as root n 6.11.5.

This is not great 👎

@paul-soporan
Copy link
Member

Closing as an external issue, there is nothing actionable on Yarn's side here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants