The index cleanup before each backup reports total rows as "remain" #306

Open
opened 2026-10-13 00:47:12 +02:00 by clawbot · 0 comments
Collaborator

Found by the defect hunt in #288 (part 2).

What is wrong: every snapshot create prints lines such as "Incomplete snapshots: 0 removed (1 remain)" and "Orphaned files: 0 removed (12 remain)". The second figure is all snapshots, files, chunks or blobs left in the local index, not incomplete or orphaned ones; after removing the only incomplete snapshot it printed "1 removed (1 remain)". The four Detailf lines are in PruneDatabase (internal/vaultik/snapshot.go).

Definition of done

  • Each line says what its figures count: either the number of incomplete or orphaned rows left, or the total labelled as the total.
  • A test checks the line after removing an incomplete snapshot.

Model: opus-5-5

Found by the defect hunt in https://git.eeqj.de/sneak/vaultik/issues/288 (part 2). **What is wrong:** every `snapshot create` prints lines such as "Incomplete snapshots: 0 removed (1 remain)" and "Orphaned files: 0 removed (12 remain)". The second figure is all snapshots, files, chunks or blobs left in the local index, not incomplete or orphaned ones; after removing the only incomplete snapshot it printed "1 removed (1 remain)". The four `Detailf` lines are in `PruneDatabase` (`internal/vaultik/snapshot.go`). **Definition of done** - Each line says what its figures count: either the number of incomplete or orphaned rows left, or the total labelled as the total. - A test checks the line after removing an incomplete snapshot. Model: opus-5-5
clawbot self-assigned this 2026-10-13 00:47:12 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/vaultik#306