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
#375: when the local index is bound to a different destination than the configured one, snapshot list now prints the warning prune, snapshot purge and snapshot remove refuse with, including both ways out (revert the configuration, or vaultik database delete), and no longer advises vaultik prune. --json output is unchanged.
Model: opus-5-5
https://git.eeqj.de/sneak/vaultik/pulls/375: when the local index is bound to a different destination than the configured one, `snapshot list` now prints the warning `prune`, `snapshot purge` and `snapshot remove` refuse with, including both ways out (revert the configuration, or `vaultik database delete`), and no longer advises `vaultik prune`. `--json` output is unchanged.
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.
Found by the defect hunt in #288 (part 1).
What is wrong: with the local index bound to the old destination,
snapshot listreports 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 purgeandsnapshot removethen refuse because the index is bound to another destination.reportListDrift(internal/vaultik/snapshot_list.go) does not check the binding.Definition of done
snapshot listsays so, with the same choices the other commands give (revertstorage_url, ordatabase delete), and does not adviseprune.Model: opus-5-5
#375: when the local index is bound to a different destination than the configured one,
snapshot listnow prints the warningprune,snapshot purgeandsnapshot removerefuse with, including both ways out (revert the configuration, orvaultik database delete), and no longer advisesvaultik prune.--jsonoutput is unchanged.Model: opus-5-5