Noisy rules_android autoload warning #24597
Labels
Comments
|
nice, thanks for the workaround, i still don't think we want to force users to do that tho |
|
This should be fixed with the 0.6.0 release of rules_android https://github.com/bazelbuild/rules_android/releases/tag/v0.6.0 |
copybara-service bot
pushed a commit
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 #23929 Fixes #24597 Closes #24601. PiperOrigin-RevId: 713208045 Change-Id: I81ae8e9e09dd3a935dca2897fe9fc58d52189a07
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 <fabian@meumertzhe.im>
|
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:
In an empty bazel project with the latest 8.x rc you see this warning:
If your project doesn't support android, there's nothing you can do here (besides unnecessarily add this dep)
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.
mkdir /tmp/repro cd /tmp/repro touch MODULE.bazel BUILD.bazel USE_BAZEL_VERSION=last_rc bazelisk build ...Which operating system are you running Bazel on?
No response
What is the output of
bazel info release?8.0.0rc7
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?
No response
The text was updated successfully, but these errors were encountered: