quak backup no longer refreshes its library on a timer (closes #183) #190

Merged

clawbot merged 2 commits from issue-183-backup-no-timed-refresh into next

2026-10-14 04:10:15 +02:00

Author	SHA1	Message	Date
sneak	1dd616f5ce	quak backup no longer refreshes its library on a timer (closes #183 ) check / check (push) Waiting to run Details The backup opened its library with the default 3-second refresh interval, so for its whole run it asked the server for changes every few seconds, and each refresh started another ML data pass. It now opens it with refreshIntervalSeconds: Infinity. The library takes Infinity as no background timer, since setTimeout would turn it into 1 ms. A refresh interval of 3600, as the read commands use, would still refresh once an hour in a backup that runs for hours. Model: opus-5-5	2026-10-14 01:39:13 +00:00
sneak	ed60a9fb44	Test: quak backup asks the server for changes only as it starts A backup whose single download is held open while the clock moves on two hours must make only the two refreshes it waits for, counted at the fake server's /collections/v2. It runs the real session loader and client against a fake of the Ente HTTP API serving one encrypted album and photo. This fails until the backup's library stops refreshing on a timer. Model: opus-5-5	2026-10-14 01:38:57 +00:00

Author

SHA1

Message

Date

sneak

1dd616f5ce

quak backup no longer refreshes its library on a timer (closes #183 )

check / check (push) Waiting to run

Details

The backup opened its library with the default 3-second refresh interval,
so for its whole run it asked the server for changes every few seconds,
and each refresh started another ML data pass. It now opens it with
refreshIntervalSeconds: Infinity. The library takes Infinity as no
background timer, since setTimeout would turn it into 1 ms. A refresh
interval of 3600, as the read commands use, would still refresh once an
hour in a backup that runs for hours.

Model: opus-5-5

2026-10-14 01:39:13 +00:00

sneak

ed60a9fb44

Test: quak backup asks the server for changes only as it starts

A backup whose single download is held open while the clock moves on two
hours must make only the two refreshes it waits for, counted at the fake
server's /collections/v2. It runs the real session loader and client
against a fake of the Ente HTTP API serving one encrypted album and photo.
This fails until the backup's library stops refreshing on a timer.

Model: opus-5-5

2026-10-14 01:38:57 +00:00