rdeps behavior differs between standard and skyquery when --notool_deps is set

[keith]

Description of the bug:

When querying for the rdeps of a file that is part of a tool with --notool_deps, the tool is returned even though it is outside of the rdeps scope (but not outside of the universe scope), only with skyquery.

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

Using this project: rdepsrepro.zip

$ USE_BAZEL_VERSION=rolling bazelisk query 'rdeps(//src/..., set(tools/main.c))'
INFO: Empty results
$ USE_BAZEL_VERSION=rolling bazelisk query --config=repro 'rdeps(//src/..., set(tools/main.c))'
//tools:main.c
//tools:tool

(flags are set in the .bazelrc)

Which operating system are you running Bazel on?

macOS

What is the output of bazel info release?

release 6.0.0-pre.20220706.4 (also repros with the latest release)

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

[haxorz]

Interesting. Just from your report, I don't have a guess what's going wrong.

--config=repro ... (flags are set in the .bazelrc)

I didn't see a .bazelrc file in your zip. What flags does --config=repro expand to?

[jpsim]

It's in the zip, but it's a hidden file since it starts with a .. Here's the contents of .bazelrc from the zip:

query --notool_deps
query --order_output=no

query:repro --universe_scope=//...

[haxorz]

ty! Didn't realize the ChromeOS file browser UI hides hidden files by default :p

[haxorz]

@shreyax Can you please triage?

[shreyax]

I will keep this issue assigned to me