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 integrity errors breaking build #49

Open
pun-ky opened this issue Nov 21, 2019 · 6 comments
Open

Yarn integrity errors breaking build #49

pun-ky opened this issue Nov 21, 2019 · 6 comments
Labels
workaround exists There is a workaround for this already

Comments

@pun-ky
Copy link

pun-ky commented Nov 21, 2019

On some dev machines, under totally strange circumstances this kicks builds using node-gradle/gradle-node-plugin :

yarnpkg/yarn#7584

current workaround for this is to run sh gradlew yarn_cache_clean

maybe sth else could be done like upgrading default version of yarn (hopefully if it was fixed in the meantime) to prevent this issue occuring in case of using this plugin?

@pun-ky
Copy link
Author

pun-ky commented Nov 21, 2019

just upgrade to default yarn version to 1.19.1 will be very appreciated

@deepy
Copy link
Member

deepy commented Nov 22, 2019

Given that 1.19.1 is the current stable that should be fine

@deepy deepy added the workaround exists There is a workaround for this already label Nov 22, 2019
@robclancy
Copy link

I'm on 1.19.2 and this still happens.

@pun-ky
Copy link
Author

pun-ky commented Dec 2, 2019

seems that yarn cache sometimes is reusable but need to be upgraded / migrated and looks like that that kind of migration may fail and end with integrity error. As I understand that, it's rather one timer and build just fails when some older version of yarn was launched before. and that cache need to be deleted. I am not sure if there will be any fix introduced that will remove a need for that cache deletion.

@robclancy
Copy link

I have to clean the cache every single time. Anything changes at all I need to do yarn cache clean and then yarn install -f --update-checksums. Super annoying.

@pun-ky
Copy link
Author

pun-ky commented Dec 3, 2019

agree, so seems that this need to be addressed somehow / more elegantly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
workaround exists There is a workaround for this already
Projects
None yet
Development

No branches or pull requests

3 participants