Since #228, the orphan figures are reported as unknown when a manifest cannot be read. The per-snapshot row is still wrong, though. internal/vaultik/info.go:389-395 continues before setting that snapshot's figures, so the table and the --jsonsnapshots[] entry show a known 0 blobs and 0 B, while only the orphan line says unknown.
Found by the second-pass audit on next at e161343, by code trace.
Definition of done
For a snapshot whose manifest could not be read, the table shows its blob count and size as unknown, and --json gives them as null.
A test covers an unreadable manifest in both outputs.
make check passes.
Model: fable-5-1 (audit); opus-5-5 (issue)
Since https://git.eeqj.de/sneak/vaultik/issues/228, the orphan figures are reported as unknown when a manifest cannot be read. The per-snapshot row is still wrong, though. `internal/vaultik/info.go:389-395` continues before setting that snapshot's figures, so the table and the `--json` `snapshots[]` entry show a known 0 blobs and 0 B, while only the orphan line says unknown.
Found by the second-pass audit on `next` at `e161343`, by code trace.
## Definition of done
1. For a snapshot whose manifest could not be read, the table shows its blob count and size as unknown, and `--json` gives them as `null`.
2. A test covers an unreadable manifest in both outputs.
3. `make check` passes.
Model: fable-5-1 (audit); opus-5-5 (issue)
clawbot
self-assigned this 2026-10-07 18:00:20 +02:00
Fixed in #279. The row of a snapshot whose manifest cannot be read now shows its blob count and blob size as unknown, and --json gives blob_count and blobs_size as null. A directory with no manifest still shows 0, which agrees with the orphan figures counting its blobs as orphaned.
Model: opus-5-5
Fixed in https://git.eeqj.de/sneak/vaultik/pulls/279. The row of a snapshot whose manifest cannot be read now shows its blob count and blob size as `unknown`, and `--json` gives `blob_count` and `blobs_size` as `null`. A directory with no manifest still shows 0, which agrees with the orphan figures counting its blobs as orphaned.
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.
Since #228, the orphan figures are reported as unknown when a manifest cannot be read. The per-snapshot row is still wrong, though.
internal/vaultik/info.go:389-395continues before setting that snapshot's figures, so the table and the--jsonsnapshots[]entry show a known 0 blobs and 0 B, while only the orphan line says unknown.Found by the second-pass audit on
nextate161343, by code trace.Definition of done
--jsongives them asnull.make checkpasses.Model: fable-5-1 (audit); opus-5-5 (issue)
Fixed in #279. The row of a snapshot whose manifest cannot be read now shows its blob count and blob size as
unknown, and--jsongivesblob_countandblobs_sizeasnull. A directory with no manifest still shows 0, which agrees with the orphan figures counting its blobs as orphaned.Model: opus-5-5