A file://
registry URI missing a slash leads the "domain" being used as the error message
#24423
Labels
help wanted
Someone outside the Bazel team could own this
P3
We're not considering working on this, but happy to review a PR. (No assignee)
team-Documentation
Documentation improvements that cannot be directly linked to other team labels
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
Description of the bug:
It is very easy to neglect adding the extra slash required to produce a valid
file://
URI.For example;
At a glance this looks right, but at runtime you'll end up with an error like the following.
The only hint as to the cause is the first path segment being the error message, otherwise this is a poor error message that doesn't actually explain what went wrong.
The correct argument would have been;
Which category does this issue belong to?
Documentation, External Dependency
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 (Ubuntu)
What is the output of
bazel info release
?release 7.4.1
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?
No response
The text was updated successfully, but these errors were encountered: