Block a user
A mistyped subcommand under snapshot, config, remote, database or completion exits 0 and does nothing
Shallow snapshot verify reports any error reading a blob's size as "Missing", and drops the error
After storage_url changes, snapshot list advises prune, which then refuses
Every restore by a non-root user warns that ownership was not preserved, even when it was
config edit fails when $EDITOR carries arguments
snapshot verify --deep --json reports "missing": 0 and "verified": 0 when it fails
Byte-size settings: the defaults and the chunk-size minimum are 1024-based while the docs, the parser and the messages are 1000-based
snapshot list and the snapshot purge listing print 1024-based sizes labelled MB, unlike every other command
snapshot list shows a NEW CHUNK SIZE of 0 B for a snapshot whose change is a modified file
snapshot create --skip-errors exits 0 and prints "Finished successfully." after skipping files
snapshot restore ignores a requested path that matches nothing, and exits 0
config set with a list index on a key that does not exist writes a map, and then no command can load the config
An invalid --keep-newer-than is checked only after the backup, which is then reported as failed and retention never runs
The index cleanup before each backup reports total rows as "remain"
Directories and symlinks are counted as files to back up on every run, so an unchanged tree reports data backed up
The "deleted" figure of a backup counts files that were not deleted since the previous snapshot of that name
Exclude patterns starting with **/ miss a match directly under the source path
A reused blob is recorded with the size of a local copy that was never stored, so snapshot verify fails on a good snapshot
A failed or interrupted backup leaves its half-written blob in the temp directory
Ctrl-C during a backup can end with "FATAL: failed to rollback transaction" and exit 1 instead of the interrupted exit