-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
New repository_ctx.original_name
produces "canonical reproducible" warnings
#25192
Labels
P1
I'll work on this now. (Assignee required)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
Comments
@bazel-io fork 8.1.0 |
FYI @Wyverald |
fmeum
added a commit
to fmeum/bazel
that referenced
this issue
Feb 4, 2025
This was referenced Feb 5, 2025
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this issue
Feb 5, 2025
Fixes bazelbuild#25192 Closes bazelbuild#25194. PiperOrigin-RevId: 723594158 Change-Id: I12aaced1db4f167c4a9691623128fe0d3eb15686
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this issue
Feb 5, 2025
Fixes bazelbuild#25192 Closes bazelbuild#25194. PiperOrigin-RevId: 723594158 Change-Id: I12aaced1db4f167c4a9691623128fe0d3eb15686
This was referenced Feb 5, 2025
A fix for this issue has been included in Bazel 8.1.0 RC2. Please test out the release candidate and report any issues as soon as possible. |
Can confirm this issue is resolved by Bazel 8.1.0 RC2, as well as the current |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P1
I'll work on this now. (Assignee required)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
Description of the bug:
Since commit 8bcfb06 introduced
repository_ctx.original_name
, closing #24467 and #25121, I've noticed the following "canonical reproducible" warnings (formatted for readability) when using thelast_green
build (at4c3863e61136a10564f01d920e4f29e142256e7c
as of the timestamp below, in Eastern Standard Time):All of these except the last are followed by stanzas similar to:
None of the following Bazel versions produce this error:
rolling
9.0.0-pre.20250121.1 (2025-01-30)Which category does this issue belong to?
External Dependency
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Note that, as I write this, mbland/rules_scala@21e4be9 is the
HEAD
of the bzlmod-bazel-8 branch of my rules_scala fork. This branch contains my work on bazelbuild/rules_scala#1482 (Bzlmod compatibility) and bazelbuild/rules_scala#1687 (Bazel 8 compatibility).Which operating system are you running Bazel on?
macOS Sequoia 15.3 (24D60)
What is the output of
bazel info release
?development version
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.Using the
last_green
build from BazeliskWhat's the output of
git remote get-url origin; git rev-parse HEAD
?If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
8bcfb06
Have you found anything relevant by searching the web?
It seems a similar problem surfaced in 2020:
Based on the above, it seems the fix may be to add
original_name
toRepositoryResolvedEvent.IGNORED_ATTRIBUTE_NAMES
at:bazel/src/main/java/com/google/devtools/build/lib/bazel/repository/RepositoryResolvedEvent.java
Lines 239 to 244 in 544887e
Any other information, logs, or outputs that you want to share?
In the bzlmod-bazel-8 branch of my rules_scala fork, which contains my work on bazelbuild/rules_scala#1482 and bazelbuild/rules_scala#1687, this causes several
dt_patches/dt_patch_test.sh
test cases to fail.The failing
test_compiler_srcjar
cases, which check for! grep "canonical reproducible"
, appear towards the end (formatting slightly to splitDEBUG:
messages on separate lines):The text was updated successfully, but these errors were encountered: