3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	3412e42af5	quak backup works on up to the content pool's limit of originals at once (closes #182) ... The backup awaited each original before starting the next, so it used one of the content pool's five slots. lib.backup(), and so quak backup, now runs as many workers as the content pool's limit (5 by default, or the contentConcurrency of the pools the library was opened with), each taking the next file from one shared list, so the limit covers the --verify hashing too. Once a worker has thrown or the lock is lost, no worker takes another file; the backup waits for the files under way and checks its lock before the ML data fetch. runBackup rejects a contentConcurrency that is not a positive integer before it takes the lock. Failed files are listed in the order they failed. Model: opus-5-5	2026-10-14 09:06:59 +02:00
clawbot	e8e8e00887	A backup whose lock is lost stops with one line, not a stack trace (closes #184) ... proper-lockfile's default onCompromised throws from a timer, so a backup whose backup.lock was removed or taken over by another backup died with a stack trace. lockBackupDirectory now returns the lock, its release function and why it was lost, and passes a handler that only records the reason. The backup checks it after the refresh and before each original, thumbnail, file's JSON and album, and before it writes failures.json, and then fails with "lost the lock on DIR: REASON", which quak backup prints as one line, exiting 1. lib.backup() takes a caller's lock as lock, in place of lockHeld: true. Releasing a lost lock leaves backup.lock alone, since it may be another backup's. Model: opus-5-5	2026-10-14 07:37:26 +02:00
clawbot	54133cfa5f	Test quak backup end to end against a fake Ente server (closes #186) ... test/cli/backup-end-to-end.test.ts runs backupCommand through run, as bin/quak.ts does, with the real loadSession reading a session saved after logging in, and every request answered by a fake of the Ente HTTP API serving data encrypted with libsodium. It covers the backup tree of an account with two albums of its own and one shared with it, a second run that downloads nothing, a download that succeeds after two 503s, a 404 recorded in failures.json with exit 1, a refresh answered 401 with exit 3, and --verify putting back an original changed on disk. The fake server and the account it logs in moved from the backup-metadata test into test/ente-server.ts, unchanged, so both tests use them. Model: opus-5-5	2026-10-14 03:38:38 +02:00