Files
vaultik/internal
sneak 08340faaa4
check / check (push) Waiting to run
Stop a backup on a symlink whose target cannot be read (closes #269)
When readlink failed, the scanner logged at debug level and left the
symlink out of the snapshot, and the run reported success even without
--skip-errors. The error now goes through the same handling as any
other entry the walk cannot read: the run aborts, or with --skip-errors
the symlink is skipped with the usual "Failed to access" error line.

A symlink removed between the walk's lstat and the readlink also
aborts the run, as an entry that vanishes during the walk already does.

Model: opus-5-5
2026-10-07 20:24:22 +00:00
..