You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two flags with the name watchfs (a deprecated startup flag and a build flag). However, the output of bazel help flags-as-proto only lists the deprecated startup flag, the build flag is missing from this dump.
This was reported in salesforce-misc/bazelrc-lsp#2, where a user of the bazelrc language server realized that the language server is showing an incorrect deprecation warning for common watchfs.
The underlying root cause is that emitFlagsAsProtoHelpuses a HashMap indexed by the flag-name to store information about all flags. This does not handle flags with colliding names correctly.
Not sure how to fix this. Either update emitFlagsAsProtoHelp or maybe just remove the deprecated watchfs startup flag for good?
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.
Run bazel help flags-as-proto, base64-decode the result and interpret it as protobuf. You will see that the watchfs flag is listed only as a startup option, and the entry for the build option is missing.
Which operating system are you running Bazel on?
not relevant
What is the output of bazel info release?
not relevant
If bazel info release returns development 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:
Description of the bug:
There are two flags with the name
watchfs
(a deprecatedstartup
flag and abuild
flag). However, the output ofbazel help flags-as-proto
only lists the deprecatedstartup
flag, the build flag is missing from this dump.This was reported in salesforce-misc/bazelrc-lsp#2, where a user of the bazelrc language server realized that the language server is showing an incorrect deprecation warning for
common watchfs
.The underlying root cause is that
emitFlagsAsProtoHelp
uses a HashMap indexed by the flag-name to store information about all flags. This does not handle flags with colliding names correctly.Not sure how to fix this. Either update
emitFlagsAsProtoHelp
or maybe just remove the deprecatedwatchfs
startup flag for good?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.
Run
bazel help flags-as-proto
, base64-decode the result and interpret it as protobuf. You will see that thewatchfs
flag is listed only as astartup
option, and the entry for thebuild
option is missing.Which operating system are you running Bazel on?
not relevant
What is the output of
bazel info release
?not relevant
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: