Skip to content

build: update checksum for io_bazel_rules_sass #24335

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

Merged
merged 1 commit into from
Feb 1, 2022

Conversation

zarend
Copy link
Contributor

@zarend zarend commented Feb 1, 2022

No description provided.

@zarend zarend requested a review from a team as a code owner February 1, 2022 19:22
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't have changed. Do we know why this sha is different all of the sudden?

@zarend
Copy link
Contributor Author

zarend commented Feb 1, 2022

I do not know. I'm getting a crash about checksum mismatch on both my mac machine and linux machine.

Error in download_and_extract: java.io.IOException: Error downloading [https://github.com/bazelbuild/rules_sass/archive/1.49.4.zip] to /usr/local/google/home/zachzach/.cache/bazel/_bazel_zachzach/b2d336703fb3d3f93dae8817b6fd6b36/external/io_bazel_rules_sass/temp8489840885666228383/1.49.4.zip: Checksum was bfb89ca97a4ad452ca5f623dfde23d2a5f3a848a97478d715881b69b4767d3bb but wanted 68b58c69cda77c4f765be92cf076400d882ea2f10d66eaf369ed69409afab5be
ERROR: no such package '@io_bazel_rules_sass//': java.io.IOException: Error downloading [https://github.com/bazelbuild/rules_sass/archive/1.49.4.zip] to /usr/local/google/home/zachzach/.cache/bazel/_bazel_zachzach/b2d336703fb3d3f93dae8817b6fd6b36/external/io_bazel_rules_sass/temp8489840885666228383/1.49.4.zip: Checksum was bfb89ca97a4ad452ca5f623dfde23d2a5f3a848a97478d715881b69b4767d3bb but wanted 68b58c69cda77c4f765be92cf076400d882ea2f10d66eaf369ed69409afab5be

#24331 looks related to this

@zarend
Copy link
Contributor Author

zarend commented Feb 1, 2022

What's also interesting is that the same error message happens to me as on CI on master https://app.circleci.com/pipelines/github/angular/components/34387/workflows/c677915b-5128-453b-8765-6604d26bbcc2/jobs/339673

Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

We should keep an eye on this, because the sha's shouldn't change.

@zarend zarend added merge safe area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release labels Feb 1, 2022
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. SHAs changing all day today.. have looked into it quite some time already..

@amysorto amysorto added the action: merge The PR is ready for merge by the caretaker label Feb 1, 2022
@amysorto amysorto merged commit a948ec4 into angular:master Feb 1, 2022
amysorto pushed a commit that referenced this pull request Feb 1, 2022
amysorto pushed a commit to amysorto/components that referenced this pull request Feb 15, 2022
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants