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
## Changes
The progress logger now only supports `append` (default) and `json`
modes.
The `json` mode is not used anywhere and is up for removal next.
## Why
In-place mode was added in #276 (March 2023) to update job progress on
the same line using ANSI escape codes. The intent was to (eventually)
show a rich UI with job status and task status but this didn't
materialize. It was only ever implemented for job run status events,
where the number of states to cycle through is minimal.
The feature was effectively disabled after commit 54e16d5 (#2213, Feb
2025) changed the default log level from `disabled` to `warn`. In-place
mode required `(log.level == "disabled" OR log.file != "stderr") AND
stderr.IsTerminal()`. With the new default, this is only met when
`log.file != "stderr"` (uncommon). Additionally, only `JobProgressEvent`
supported in-place updates while other events fell back to append mode.
Before (when forcing in-place mode):
```
Run URL: ...
2025-10-23 16:45:01 "Test Progress Logger" TERMINATED SUCCESS
```
After:
```
Run URL: ...
2025-10-23 16:46:28 "Test Progress Logger" RUNNING
2025-10-23 16:47:09 "Test Progress Logger" TERMINATED SUCCESS
```
Related: the escape codes that were used are not VT100 compliant and
don't work in Ghostty.
## Tests
Tests pass. Manually confirmed `bundle run` works as expected.
0 commit comments