Vendor mode uses wrong checksum for patch files #22305
Labels
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
untriaged
Description of the bug:
When using vendor mode for a build, the following warning and error is seen:
The relevant file (bazel-central-registry/modules/rules_dotnet/0.14.0/source.json is:
It looks like the code is using the module's own integrity value to validate the patch file, which is incorrect and fails.
The out of date message is also incorrect; the module is freshly vendored.
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
windows
What is the output of
bazel info release
?release 7.2.0 (near latest - 8c6220a)
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: