The status and progress lines of remote info and snapshot verify now go through internal/ui, as the README's output style section says, so they carry the marker and, on a terminal, color. These are the lines the issue lists:
remote info: three Beginf lines.
Shallow snapshot verify: one Beginf line.
snapshot verify --deep: Beginf, Completef and the per-blob Progressf heartbeat, with its two leading spaces dropped because Progressf indents.
Report lines, headers and summaries stay on stdoutf. The existing if guards are unchanged, so these lines are still suppressed under --json as well as --quiet.
Tests: TestRemoteInfo_StatusLineUsesUIMarker and TestVerify_DeepStatusLineUsesUIMarker check that the marker appears on one line each, and that the line is absent under --quiet.
Under host load, the internal/vaultik package's tests come close to the 90s go test -timeout in the Dockerfile. One make check run exceeded it, in tests this change does not touch.
Model: opus-5-5
Closes https://git.eeqj.de/sneak/vaultik/issues/410.
The status and progress lines of `remote info` and `snapshot verify` now go through `internal/ui`, as the README's output style section says, so they carry the marker and, on a terminal, color. These are the lines the issue lists:
- `remote info`: three `Beginf` lines.
- Shallow `snapshot verify`: one `Beginf` line.
- `snapshot verify --deep`: `Beginf`, `Completef` and the per-blob `Progressf` heartbeat, with its two leading spaces dropped because `Progressf` indents.
Report lines, headers and summaries stay on `stdoutf`. The existing `if` guards are unchanged, so these lines are still suppressed under `--json` as well as `--quiet`.
Tests: `TestRemoteInfo_StatusLineUsesUIMarker` and `TestVerify_DeepStatusLineUsesUIMarker` check that the marker appears on one line each, and that the line is absent under `--quiet`.
Under host load, the `internal/vaultik` package's tests come close to the 90s `go test -timeout` in the Dockerfile. One `make check` run exceeded it, in tests this change does not touch.
Model: opus-5-5
PASS: the status and progress lines of remote info and snapshot verify now go through internal/ui exactly as #410 lists, with nothing else changed.
Model: opus-5-5
PASS: the status and progress lines of `remote info` and `snapshot verify` now go through `internal/ui` exactly as https://git.eeqj.de/sneak/vaultik/issues/410 lists, with nothing else changed.
Model: opus-5-5
For the reworker: rebase onto current origin/next. The only conflict is the "Completed Steps" list in TODO.md; keep both entries, newest first. Change nothing else. Run make check, push with --force-with-lease, and reply here in one line.
Model: opus-5-5
For the reworker: rebase onto current `origin/next`. The only conflict is the "Completed Steps" list in `TODO.md`; keep both entries, newest first. Change nothing else. Run `make check`, push with `--force-with-lease`, and reply here in one line.
Model: opus-5-5
The status and progress lines of `remote info` and `snapshot verify`
(shallow and deep) now use the `internal/ui` Begin, Complete and
Progress methods, so they carry its marker and, on a terminal, color.
The reports themselves stay plain on stdout.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #410.
The status and progress lines of
remote infoandsnapshot verifynow go throughinternal/ui, as the README's output style section says, so they carry the marker and, on a terminal, color. These are the lines the issue lists:remote info: threeBeginflines.snapshot verify: oneBeginfline.snapshot verify --deep:Beginf,Completefand the per-blobProgressfheartbeat, with its two leading spaces dropped becauseProgressfindents.Report lines, headers and summaries stay on
stdoutf. The existingifguards are unchanged, so these lines are still suppressed under--jsonas well as--quiet.Tests:
TestRemoteInfo_StatusLineUsesUIMarkerandTestVerify_DeepStatusLineUsesUIMarkercheck that the marker appears on one line each, and that the line is absent under--quiet.Under host load, the
internal/vaultikpackage's tests come close to the 90sgo test -timeoutin the Dockerfile. Onemake checkrun exceeded it, in tests this change does not touch.Model: opus-5-5
PASS: the status and progress lines of
remote infoandsnapshot verifynow go throughinternal/uiexactly as #410 lists, with nothing else changed.Model: opus-5-5
For the reworker: rebase onto current
origin/next. The only conflict is the "Completed Steps" list inTODO.md; keep both entries, newest first. Change nothing else. Runmake check, push with--force-with-lease, and reply here in one line.Model: opus-5-5
bbe39fa073to28597dcff8Rebased onto
next; inTODO.mdthis change's entry now sits above theconfig initentry, and nothing else changed.Model: opus-5-5