Refresh recently used addons in the background

namillis commented

2026-10-09 19:48:21 +00:00

Owner

Data only refreshed when someone opened a catalog, and the catalog was served from whatever was cached before the refresh finished. After two quiet days (last refresh Oct 7 1:33 PM), the first Live Now on Oct 9 was built from 2-day-old guides and showed 2 events. It showed 100 once the refresh finished a few minutes later.

Any addon that serves a catalog is now added to a set. Every 5 minutes, addons in that set refresh if their data is due (the same needsRefresh check as before, so still hourly with EPG_REFRESH_MS). The tick also starts the ESPN scoreboard refresh when it's stale. An addon that hasn't been opened in 7 days drops out of the set and goes back to refreshing only when it's opened, so old configs don't keep hitting providers.

Tested in the running container with stand-in addons and the real pool loaded from Redis, without contacting providers: a stale addon is refreshed, a fresh one and one idle for over 7 days are not, an idle one rejoins when opened, and the pool refreshes only once its data is over an hour old.

Data only refreshed when someone opened a catalog, and the catalog was served from whatever was cached before the refresh finished. After two quiet days (last refresh Oct 7 1:33 PM), the first Live Now on Oct 9 was built from 2-day-old guides and showed 2 events. It showed 100 once the refresh finished a few minutes later. Any addon that serves a catalog is now added to a set. Every 5 minutes, addons in that set refresh if their data is due (the same `needsRefresh` check as before, so still hourly with `EPG_REFRESH_MS`). The tick also starts the ESPN scoreboard refresh when it's stale. An addon that hasn't been opened in 7 days drops out of the set and goes back to refreshing only when it's opened, so old configs don't keep hitting providers. Tested in the running container with stand-in addons and the real pool loaded from Redis, without contacting providers: a stale addon is refreshed, a fresh one and one idle for over 7 days are not, an idle one rejoins when opened, and the pool refreshes only once its data is over an hour old.

namillis added 1 commit

2026-10-09 19:48:21 +00:00

Refresh recently used addons in the background so the first catalog after a quiet stretch isn't built from old guides 3e5ea69afb

namillis merged commit fb48def2af into main

2026-10-09 19:52:56 +00:00

namillis referenced this pull request from a commit

2026-10-09 19:52:56 +00:00

Merge pull request 'Refresh recently used addons in the background' (#2) from fix/background-refresh into main

namillis deleted branch fix/background-refresh

2026-10-09 19:52:59 +00:00

namillis referenced this pull request

2026-10-09 19:59:18 +00:00

Put the provider pool on the background refresh timer at startup #4

Rows
Columns

Refresh recently used addons in the background #2