Incorrect error from cquery when configuration flag has the default value

Description of the bug:

cquery produces incorrect error transition inputs [@//:flavor] do not correspond to valid settings when the flag is not set on the command line or set to the default value.

What’s the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Minimal repro provided here: https://github.com/Bazel-snippets/cquery_transition_error

The following command demonstrates the incorrect error: bazel cquery somepath(transistor,dummy) --transitions=lite --//:flavor=opt

Error: transition inputs [@//:flavor] do not correspond to valid settings

Omiting of the flag flavoror setting it to the default value opt causes the error. Setting it to dbg avoids the error.

Using --transitions=lite and somepath query function both required to reproduce the problem.

Which operating system are you running Bazel on?

Mac, Linux, Windows

What is the output of bazel info release?

5.2

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 master; git rev-parse HEAD ?

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

[fmeum]

@sgowroji This is also missing from the original report, but you have to enclose the bazel query query in single quotes or the shell will choke on the ( in the query.

This should work:

bazel cquery 'somepath(transistor,dummy)' --transitions=lite --//:flavor=dbg

[gregestren]

Oh sorry, I didn’t see the “not a bug” tag.