vaultik

321 Commits 2 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	fa56165fe4	Stop a cancelled backup at once under --skip-errors (closes #286 ) check / check (push) Waiting to run Details After Ctrl-C or SIGTERM, phase 2 of a --skip-errors backup treated the cancellation error from each remaining file like an unreadable file: it opened the file, printed an error line, counted it as failed and moved on to the next. The processing loop now checks for cancellation before each file, and an error from a file once the run is cancelled stops the run instead of being skipped. The loop check is what stops a run cancelled while an empty file is open, since an empty file has no chunks and nothing reads the context while it is backed up. The --skip-errors test helper now takes the scan's context. Model: opus-5-5	2026-10-08 15:12:07 +02:00
clawbot	e459a66099	Stop a backup on a symlink whose target cannot be read (closes #269 ) check / check (push) Waiting to run Details 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-08 00:12:13 +02:00
clawbot	b4654f8e52	Abort the run when packing fails, even under --skip-errors (closes #161 ) check / check (push) Successful in 1m22s Details check / check (pull_request) Successful in 3m2s Details A chunk is registered as pending (known, scanner-pending, packer pending-row) before it is packed. Under --skip-errors the scanner skipped a file on any processing error, including a failure inside addChunkToPacker (packing, database, encryption, upload). The pending chunk then stayed queued and a later blob finalize inserted it into the chunks table with no blob_chunks row, so a snapshot could complete holding a file whose chunk is in no blob and cannot be restored. Errors from addChunkToPacker are now marked and abort the run regardless of --skip-errors; only open and read errors are skipped. The bookkeeping order is unchanged. Flag help and comments now say only unreadable files are skipped. Model: opus-4-8	2026-09-22 12:28:44 +02:00

Author

SHA1

Message

Date

clawbot

fa56165fe4

Stop a cancelled backup at once under --skip-errors (closes #286 )

check / check (push) Waiting to run

Details

After Ctrl-C or SIGTERM, phase 2 of a --skip-errors backup treated the
cancellation error from each remaining file like an unreadable file: it
opened the file, printed an error line, counted it as failed and moved
on to the next. The processing loop now checks for cancellation before
each file, and an error from a file once the run is cancelled stops the
run instead of being skipped. The loop check is what stops a run
cancelled while an empty file is open, since an empty file has no
chunks and nothing reads the context while it is backed up.

The --skip-errors test helper now takes the scan's context.

Model: opus-5-5

2026-10-08 15:12:07 +02:00

clawbot

e459a66099

Stop a backup on a symlink whose target cannot be read (closes #269 )

check / check (push) Waiting to run

Details

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-08 00:12:13 +02:00

clawbot

b4654f8e52

Abort the run when packing fails, even under --skip-errors (closes #161 )

check / check (push) Successful in 1m22s

Details

check / check (pull_request) Successful in 3m2s

Details

A chunk is registered as pending (known, scanner-pending, packer pending-row) before it is packed. Under --skip-errors the scanner skipped a file on any processing error, including a failure inside addChunkToPacker (packing, database, encryption, upload). The pending chunk then stayed queued and a later blob finalize inserted it into the chunks table with no blob_chunks row, so a snapshot could complete holding a file whose chunk is in no blob and cannot be restored.

Errors from addChunkToPacker are now marked and abort the run regardless of --skip-errors; only open and read errors are skipped. The bookkeeping order is unchanged. Flag help and comments now say only unreadable files are skipped.

Model: opus-4-8

2026-09-22 12:28:44 +02:00