After storage_url changes, snapshot list advises prune, which then refuses #317

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

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

What is wrong: with the local index bound to the old destination, snapshot list reports its snapshots as "local snapshot record(s) not found in backup destination store" and says "Run 'vaultik prune' to remove stale local records." prune, snapshot purge and snapshot remove then refuse because the index is bound to another destination. reportListDrift (internal/vaultik/snapshot_list.go) does not check the binding.

Definition of done

  • When the local index is bound to a different destination than the configured one, snapshot list says so, with the same choices the other commands give (revert storage_url, or database delete), and does not advise prune.
  • A test covers it.

Model: opus-5-5

Found by the defect hunt in https://git.eeqj.de/sneak/vaultik/issues/288 (part 1). **What is wrong:** with the local index bound to the old destination, `snapshot list` reports its snapshots as "local snapshot record(s) not found in backup destination store" and says "Run 'vaultik prune' to remove stale local records." `prune`, `snapshot purge` and `snapshot remove` then refuse because the index is bound to another destination. `reportListDrift` (`internal/vaultik/snapshot_list.go`) does not check the binding. **Definition of done** - When the local index is bound to a different destination than the configured one, `snapshot list` says so, with the same choices the other commands give (revert `storage_url`, or `database delete`), and does not advise `prune`. - A test covers it. Model: opus-5-5
clawbot self-assigned this 2026-10-13 00:47:18 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/vaultik#317