Fail restore for a requested path that matches nothing (closes #309)

snapshot restore said nothing about a requested path that matched no entry in the snapshot (a typo, a relative path, or a path through a symlinked snapshot path, whose entries are stored under the resolved directory) and exited 0, even when nothing matched. Each such path is now named in a warning as soon as the file list is built, so it shows even when the restore then stops on an error, and restore returns an error after restoring the paths that do match. The restore summary moved into finishRestore to keep Restore within the length limit. Making a path through a symlink match is not part of this change. Judgement call: when the restore itself fails, that error is returned. Model: opus-5-5
2026-10-13 23:14:22 +02:00
parent 37d525c322
commit 2c087be577
4 changed files with 262 additions and 25 deletions
@@ -30,6 +30,8 @@ This command will restore files from the specified snapshot to the
 target directory.
 If no paths are specified, all files are restored.
 If paths are specified, only matching files/directories are restored.
+A path that matches nothing in the snapshot is named in a warning, and
+the command exits non-zero after restoring the paths that match.

 The snapshot may be named by its ID or, when restoring on a host with no
 local index, by the remote key that 'snapshot list' prints for a