Open laurentlb opened 1 month ago
We are actually not sure about what information should be shown, feel free to make a suggestion!
I guess it would be useful to print information to find where it comes from (e.g. lines in the MODULE file). I don't know if this information is available anywhere else.
But the same module could be referenced in different MODULE.bazel file. If you want to know, why a specific version of the module is selected, you can try bazel mod graph
?
Description of the bug:
The command
bazel mod show_repo
includes a stacktrace at the end of the output. In most cases, it just says<builtin> in <toplevel>
, which doesn't give any information. I'd expect for example to get the line ofbazel_dep
in a MODULE.bazel file.Example:
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?
No response
What is the output of
bazel info release
?No response
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
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
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