search

ramasilveyra / gitpkg

Publish packages as git tags
MIT License
274 stars 28 forks source link

Yarn cache bug #12

Closed luwes closed 2 years ago

luwes commented 6 years ago

Gitpkg is affected by the same bug reported here by me. https://github.com/yarnpkg/yarn/issues/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 commented 6 years ago

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 commented 2 years ago

Closing due to inactivity