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

Yarn cache bug #12

Closed
luwes opened this issue Sep 16, 2018 · 2 comments
Closed

Yarn cache bug #12

luwes opened this issue Sep 16, 2018 · 2 comments

Comments

@luwes
Copy link

luwes commented Sep 16, 2018

Gitpkg is affected by the same bug reported here by me.
yarnpkg/yarn#6256

The root issue is that a git pull on the cached repo will not pull in the standalone tags (not reachable from the heads).

Related question on Stackoverflow:
https://stackoverflow.com/questions/16678072/fetching-all-tags-from-a-remote-with-git-pull/27911598

Bug

What is the current behavior?

yarn install fails to install subsequent Github URL packages with format
git+ssh://git@github.com:luwes/chameleon.git#cricket-v0.0.1-beta.3
git+ssh://git@github.com:luwes/chameleon.git#grasshopper-v0.0.1-beta.4

error Command failed.
Exit code: 128

screen shot 2018-08-09 at 14 22 00

What is the expected behavior?

yarn install installs the package

Node 10.6.0, Yarn 1.9.4, MacOS 10.13.3

@ramasilveyra
Copy link
Owner

Hello! Thanks for the heads up!

Yes I have seen this issue on some builds at my current company. It seems like a cache bug in yarn related to the git private deps. Last time I failed to create an isolated repro.

As a workaround:

yarn cache clean

or

yarn cache clean <dep name>

@ramasilveyra
Copy link
Owner

Closing due to inactivity

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

2 participants