feat: one Poll Lane per Site, replacing the shared pace (#100) #106
Reference in New Issue
Block a user
Delete Branch "feat/100-poll-lanes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #100.
Each Site runs its own Poll Lane: an independent goroutine with its own rest
and pace from the registry (
backend/internal/latest/sites.go), replacing theshared cooldown/interval/stagger/batch configuration. Rest (1h, all six Sites
including the browser trio) is enforced by the due query's WHERE clause; the
Lane sleeps its effective gap between fetches — the registry 10s, or
rest/eligible when a Site holds enough Series, floored at 1s with a
Site-naming warning when the floor engages.
Lane-local failure handling:
their stamp, untried Series stay due.
their passes for the same 15m (no stamp-per-pass-per-Lane on a dead tab),
then decay and probe again.
shared by the three browser Sites; "browser lane behind by X" logged every
pass.
page) runs in the background so a slow CDN cannot consume a Lane's gap.
Removed:
LATEST_CHAPTER_POLL_{COOLDOWN,BROWSER_COOLDOWN,INTERVAL,BATCH,STAGGER}and the 6h browser rest. Only
LATEST_CHAPTER_POLL_ENABLEDremains; DEPLOY.mddocuments the exact
.envedit. ADR-0010 records the decisions.