From the acceptance test (#418): a basic a user of a backup tool expects and does not find.
What is missing
No way to see what a backup would include before running it. The only way to check an exclude pattern today is a real backup followed by a restore (which is what the test had to do). The same first run also binds the local index to the destination.
Why a user expects it
The default config carries about a hundred exclude patterns and the README documents their matching rules; a user who adds one wants to see it work before paying for an upload. restic backup --dry-run and borg create --dry-run exist for this reason.
What it would take
snapshot create --dry-run: run the scanner only, write nothing to the index or the destination, and print the summary the real run prints (files examined, to back up, bytes, and the count of excluded entries); with --verbose, each excluded path and the pattern that matched it. Optionally check that the destination accepts a write, so a wrong bucket or key is found here rather than by the first backup.
Model: fable-5-1
From the acceptance test (https://git.eeqj.de/sneak/vaultik/issues/418): a basic a user of a backup tool expects and does not find.
**What is missing**
No way to see what a backup would include before running it. The only way to check an exclude pattern today is a real backup followed by a restore (which is what the test had to do). The same first run also binds the local index to the destination.
**Why a user expects it**
The default config carries about a hundred exclude patterns and the README documents their matching rules; a user who adds one wants to see it work before paying for an upload. `restic backup --dry-run` and `borg create --dry-run` exist for this reason.
**What it would take**
`snapshot create --dry-run`: run the scanner only, write nothing to the index or the destination, and print the summary the real run prints (files examined, to back up, bytes, and the count of excluded entries); with `--verbose`, each excluded path and the pattern that matched it. Optionally check that the destination accepts a write, so a wrong bucket or key is found here rather than by the first backup.
Model: fable-5-1
sneak
was assigned by clawbot2026-11-11 01:02:06 +01:00
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.
From the acceptance test (#418): a basic a user of a backup tool expects and does not find.
What is missing
No way to see what a backup would include before running it. The only way to check an exclude pattern today is a real backup followed by a restore (which is what the test had to do). The same first run also binds the local index to the destination.
Why a user expects it
The default config carries about a hundred exclude patterns and the README documents their matching rules; a user who adds one wants to see it work before paying for an upload.
restic backup --dry-runandborg create --dry-runexist for this reason.What it would take
snapshot create --dry-run: run the scanner only, write nothing to the index or the destination, and print the summary the real run prints (files examined, to back up, bytes, and the count of excluded entries); with--verbose, each excluded path and the pattern that matched it. Optionally check that the destination accepts a write, so a wrong bucket or key is found here rather than by the first backup.Model: fable-5-1