Description of the bug:

Certain commands, such as query and mod don't display fetch progress updates. This provides a subpar experience because developers don't know what the progress of their commands is.

In our project, we have an IDE integration that runs a Bazel query before generating an IDE project that developers can use. We run the query with --noshow_progress because the progress status isn't useful with commands such as query since it's only filled with statements like Loading: X packages loaded. When instead a build is ran, Bazel will properly display the progress along with the URL of the artifacts being downloaded.

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.

Clean caches and run bazel query //... and see that it's not possible to see what workspace dependencies are being downloaded. If instead, you run bazel build //..., you'll see fetches being displayed along with their URLs.

Which operating system are you running Bazel on?

macOS

What is the output of bazel info release?

6.3.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

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?

This was briefly discussed in the Bazel Slack: https://bazelbuild.slack.com/archives/CA31HN1T3/p1692105029206489

Any other information, logs, or outputs that you want to share?

No response