Malformed bazel query
command crashes with "Illegal char <*> at index" on Windows
#15962
Labels
area-Windows
Windows-specific issues and feature requests
P2
We'll consider working on this in future. (Assignee optional)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
type: bug
Description of the bug:
It looks like using a malformed (?)
bazel query
command can crash Bazel on Windows:Even if the command is invalid, it should probably not crash Bazel.
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Which operating system are you running Bazel on?
Windows 10
What is the output of
bazel info release
?release 5.2.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 master; git rev-parse HEAD
?No response
Have you found anything relevant by searching the web?
There are mutliple other "Illegal char <...> at index" issues at this GitHub repository here, though all are closed (not sure if all are really fixed however).
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: