WARNING: Couldn't auto load rules or symbols #23929
Assignees
Labels
P2
We'll consider working on this in future. (Assignee optional)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
team-Rules-API
API for writing rules/aspects: providers, runfiles, actions, artifacts
type: bug
Comments
Wyverald
added
team-ExternalDeps
|
cc @comius |
|
You may silence the warning by removing rules_android and protobuf from incompatible_autoload_externally. At the moment that means setting it to „+@rules_java,+@rules_python,+@rules_shell“. Futhermore if you have load statements for some of the remaining rules or if you’re not using them, you may also omit them from the flag. |
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this issue
Jan 8, 2025
…port This reduces noise while giving users more actionable information when they actually use a symbol that failed to autoload. Also ensures that modules with legacy repo names (`com_google_protobuf` and `build_bazel_apple_support`) are handled correctly. Fixes bazelbuild#23929 Fixes bazelbuild#24597 Closes bazelbuild#24601. PiperOrigin-RevId: 713208045 Change-Id: I81ae8e9e09dd3a935dca2897fe9fc58d52189a07
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 8, 2025
…name support (#24856) This reduces noise while giving users more actionable information when they actually use a symbol that failed to autoload. Also ensures that modules with legacy repo names (`com_google_protobuf` and `build_bazel_apple_support`) are handled correctly. Fixes #23929 Fixes #24597 Closes #24601. PiperOrigin-RevId: 713208045 Change-Id: I81ae8e9e09dd3a935dca2897fe9fc58d52189a07 Commit eba2054 Co-authored-by: Fabian Meumertzheim <[email protected]>
13 tasks
|
A fix for this issue has been included in Bazel 8.0.1 RC1. Please test out the release candidate and report any issues as soon as possible. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug:
I've tried out 8.0.0rc1 on our codebase, and we're seeing
We're not actively using either of these rules in our codebase, but I wouldn't rule out that we have them as transitive dependencies in our dependency tree.
We're using bzlmod, our WORKSPACE file exists and is empty.
How can we silence these warnings? They are not helpful for us, and I'd be reluctant to roll out this upgrade to our users, as they'll be confused by warnings that aren't actionable or relevant to them.
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?
macos
What is the output of
bazel info release?8.0.0rc1
If
bazel info releasereturnsdevelopment versionor(@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
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
Slack discussion: https://bazelbuild.slack.com/archives/CA31HN1T3/p1728481396695989
The text was updated successfully, but these errors were encountered: