5 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	7f9bf5eb90	Test: lib.backup() starts no further original once its lock is lost ... Issue 184 made the backup check its lock before each original. The workers that now back up several originals at once take the next file without checking it. With five downloads waiting, backup.lock is removed and proper-lockfile's timer finds it gone. The backup must download no other photo, and reject with "lost the lock on DIR" once those five are in place. Today its workers go on to the other three photos. Model: opus-5-5	2026-10-14 06:34:09 +00:00
sneak	9f6fa1990f	Test: lib.backup() rejects only once its workers have stopped when onProgress throws ... With a content pool of eight, all eight downloads wait at once. Photo 103's is answered 404 and the line reporting it throws while the other seven still wait. When lib.backup() rejects, the other seven originals must be in place and the lock gone, so nothing is written after the backup has ended. Today the backup rejects as soon as that one worker throws, before the others have written anything. Model: opus-5-5	2026-10-14 06:34:09 +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
sneak	36d7cdd5db	Test: lib.backup() works on up to the content pool's limit of originals at once ... Against the fake Ente server, with each download held until the test lets it go: a library with the default pools has five downloads in flight and a pool of two has two; with verify, only the originals whose downloads are in flight have been hashed; a 404 for one photo does not stop the rest; and two runs end the same with a pool of one as with the default pools. Today the backup downloads one original at a time, so the first four fail. Model: opus-5-5	2026-10-14 06:33:55 +00:00