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

Error fetching dependencies in node >= 8 #3703

Closed
ebitonte opened this issue Jun 22, 2017 · 5 comments
Closed

Error fetching dependencies in node >= 8 #3703

ebitonte opened this issue Jun 22, 2017 · 5 comments

Comments

@ebitonte
Copy link

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

What is the current behavior?
When running yarn with a clean cache on node v8.1.2, receive an error during Fetching packages with the following message:

Cannot read property 'asyncReset' of null"

This behavior is inconsistent, and appears to be a race condition within node 8.

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

Within a project (with a large number of dependencies so as to increase chances of hitting race condition...)

rm -rf node_modules
yarn cache clean
yarn

What is the expected behavior?
Successful fetching of all packages 😄

Please mention your node.js, yarn and operating system version.
node: 8.1.2
yarn: 0.24.6, 0.23.4
MacOS: 10.12.5

@ebitonte
Copy link
Author

I've made a test repo in which I'm able to very consistently reproduce this error

https://github.com/ebitonte/yarn-test

@voxsim
Copy link
Contributor

voxsim commented Jul 11, 2017

Can I help on this? I also have some other issues related to node 8.. should we build everything for node 8 too? For everything I mean:

  • generate an artifact for node8
  • add a travis/circleci/appveyor build
  • maybe a babel part for node8 too
  • everything that I don't know that we already do for node4, node6 :p

@BYK
Copy link
Member

BYK commented Jul 28, 2017

@ebitonte I cannot reproduce with latest master with node 8.1.3. Can you verify if this is also the case for you.

FYI I had to replace all your internal npm mirror paths with https://registry.npmjs.org/ in the yarn.lock file with the repo you've provided for repro.

@BYK
Copy link
Member

BYK commented Aug 7, 2017

Closing since the author did not respond to our requests for more info.

@ebitonte feel free to reopen this if you can provide more information and can reproduce the issue.

@BYK BYK closed this as completed Aug 7, 2017
@MMX13
Copy link

MMX13 commented Aug 8, 2017

I am also having the same issue with a project with a large number of dependencies. I've also reproduced the same issue using @ebitonte's test repo (after removing the yarn.lock)

On three separate runs it failed on different packages.
error An unexpected error occurred: "http://registry.npmjs.org/accepts: Cannot read property 'asyncReset' of null".
error An unexpected error occurred: "http://registry.npmjs.org/on-headers: Cannot read property 'asyncReset' of null".
error An unexpected error occurred: "http://registry.npmjs.org/compressible: Can not read property 'asyncReset' of null".

yarn v0.27.5
node 8.2.1
Win7

Edit: Yarn successfully installed the dependencies after I rolled back node to v6.11.2

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

No branches or pull requests

5 participants