protocolbuffers / protocolbuffers/protobuf
36.0 macOS prebuilt Bazel tool integrity hashes do not match artifacts
Open
Beginner friendly
Nobody has claimed this yet.
bug
packaging & distribution
- Dominant language
- C++
- Stars
- 72k
- Forks
- 16.3k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 140
Description
$ curl -sSL https://github.com/protocolbuffers/protobuf/releases/download/v36.0/protobuf-36.0.bazel.tar.gz | tar -xzO protobuf-36.0/bazel/private/oss/toolchains/prebuilt/tool_integrity.bzl | grep osx-aarch_64
"protoc-36.0-osx-aarch_64.zip": "726141c541c84a01cdc501ae6c0c845d2dda26414ccf42e641ed096e7491344f",
$ curl -sSL https://github.com/protocolbuffers/protobuf/releases/download/v36.0/protoc-36.0-osx-aarch_64.zip | sha256sum
b6bc4afdcb880124bf342851d05155b6e3d9b6e661236d87b9c614250d26ae00 -
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect bazel/private/oss/toolchains/prebuilt/tool_integrity.bzl in the v36.0 Bazel archive and compare its osx-aarch_64 entry with the SHA-256 output for protoc-36.0-osx-aarch_64.zip. The work is done when the recorded integrity hash matches the published artifact.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 82/100