-
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
crash on invalid repository name
in bazel 8.0.0
#24621
Comments
Some more digging (with a I don't know whether you consider crashing on this a bug or not, so feel free to close the issue if not 👍 |
Yeah, ideally Bazel should fail more gracefully, but at least this time it crashed with some useful information. |
Fixes bazelbuild#24621 Closes bazelbuild#24666. PiperOrigin-RevId: 708009380 Change-Id: I8706f1fdfba2282a27e84dff610e6511c1060e23
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. |
Description of the bug:
I'm trying to upgrade to 8.0.0 but bazel crashes with
invalid repository name
no matter what target I'm trying to build.I've both rm'd
MODULE.bazel.lock
and ranbazel clean --expunge
.@fmeum suggested on slack that this is likely a
rules_python
bug, but that bazel probably shouldn't crash on this anyway.Which category does this issue belong to?
Core
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?
Linux 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux
What is the output of
bazel info release
?release 8.0.0
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
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?
The crash with stacktrace:
The text was updated successfully, but these errors were encountered: