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

Fix "Invalid value type 175:0 in yarn.lock" #48584

Merged
merged 1 commit into from
Jun 27, 2023

Conversation

skipkayhil
Copy link
Member

@skipkayhil skipkayhil commented Jun 27, 2023

Motivation / Background

Something about the update to yarn.lock appears to have corrupted it, and 6-1-stable CI is now failing with the above error.

https://buildkite.com/rails/rails/builds/97539#0188f9ac-db37-4c8e-8be7-0da2fc4fc0c9

Detail

This commit fixes the issue by regenerating the lockfile:

rm yarn.lock && yarn install

Checklist

Before submitting the PR make sure the following are checked:

  • This Pull Request is related to one change. Changes that are unrelated should be opened in separate PRs.
  • Commit message has a detailed description of what changed and why. If this PR fixes a related issue include it in the commit message. Ex: [Fix #issue-number]
  • Tests are added or updated if you fix a bug or add a feature.
  • CHANGELOG files are updated for the changed libraries if there is a behavior change or additional feature. Minor bug fixes and documentation changes should not be included.

Something about the update to yarn.lock appears to have corrupted it,
and 6-1-stable CI is now failing with the above error.

This commit fixes the issue by regenerating the lockfile:

`rm yarn.lock && yarn install`
@matthewd matthewd merged commit dd410b5 into rails:6-1-stable Jun 27, 2023
0 of 2 checks passed
@skipkayhil skipkayhil deleted the hm-fix-corrupt-yarn-lock branch June 27, 2023 13:55
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

Successfully merging this pull request may close these issues.

None yet

2 participants