4 Commits

Include renames

Author	SHA1	Message	Date
sneak	767545f4ab	Test: lib.backup() takes no new original once onProgress has thrown or its lock is lost ... The onProgress test now runs eight photos with a pool of five and holds only the first five downloads, so a backup that went on after the throw would download and store the other three. The end-to-end test of a removed backup.lock expects the backup to stop after its three originals, before it fetches ML data. Model: opus-5-5	2026-10-14 06:37:26 +00:00
sneak	8904477f75	quak backup works on up to the content pool's limit of originals at once (closes #182) ... lib.backup() ran its originals one at a time, so the content pool's five slots, or the contentConcurrency of the pools a library was opened with, went unused. The work for one original, its verify hashing included, is now storeOriginal, and that many workers take files from one iterator over the backup's files, so no more originals than the limit are open at once. BackupLibrary gains contentConcurrency, which the library sets from its content pool. The README's "Request pools" says so. The tests of a backup whose lock is lost now expect all three originals downloaded, since all three are under way at once. Model: opus-5-5	2026-10-14 06:34:09 +00: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