-
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
more Extracting tar content of undefined failed woes in yarn 1.17.3 #7544
Comments
+1 . Happening with Bitrise CI |
Same happening here.. |
having the same issue with yarn 1.22.4 |
Happening with yarn 1.22.4. Gitlab CI. Not reproducible on local machine however. |
FYI, I attempted to solve one of the root causes for this issue in #8182, still waiting for someone to review it. |
For anyone still needing a solution, I've changed our git repo dependency to remove its |
Also experiencing on 1.22.4 and like @alecgerona it seems to coincide with a package that has a |
I've been having this issue and fixed it by moving from a parallel install of dependencies to synchronous (two different yarn install commands for a server/client in a mono-repo). Not sure if that will be helpful to anyone. |
I am using yarn
1.17.3
Do you want to request a feature or report a bug?
bug
What is the current behavior?
An example of what is happening is here:
Happens occasionally and can be any dependency.
There are many, many, many similar issues on the issue tracker including #7087, #6755, #6312
Most say it is a git URL in the package.json or lock file but I don't have any of those.
Other solutions say to use
yarn install --network-concurrency 1
But this is a poor solution in a CI pipeline with lots of builds at any time.
If the current behavior is a bug, please provide the steps to reproduce.
I cannot reproduce it consistently, seems to happen when the CI server isunder load.
What is the expected behavior?
No cache problems
Please mention your node.js, yarn and operating system version.
node 8.11.3
The text was updated successfully, but these errors were encountered: