bazelbuild/bazel

`--curses=no` has almost no information about analysis phase

Open

#23,522 opened on Sep 5, 2024

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Java (4,465 forks)batch import
P3help wantedteam-CLItype: feature request

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 22d 20h) (77 merged PRs in 30d)

Description

Description of the feature request:

When specifying --curses=no, there's almost no information about the analysis phase (what's being downloaded, while repo rules and modexts are being executed etc.) printed. That's a shame, as --curses=yes has a lot of interesting info about that.

Which category does this issue belong to?

No response

What underlying problem are you trying to solve with this feature?

GitHub actions logs with --curses=auto behaves as --curses=no, which makes our CI logs not very useful when it comes to guesstimating what's going on in the analysis phase.

Which operating system are you running Bazel on?

Ubuntu 22.04

What is the output of bazel info release?

7.3.1

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

Have you found anything relevant by searching the web?

No response

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

No response

Contributor guide

Research direction
Examine the Bazel source code to understand how the analysis phase prints progress information and how the curses flag affects the output. Look for relevant code in the OutputService or EventBus classes.
Tech stack
java
Domain
build system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70