feat(latest): split browser poll cooldown #48
Reference in New Issue
Block a user
Delete Branch "issue-42-browser-cooldown"
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?
Summary
Split latest-chapter polling cooldowns by fetch cost. Browser-backed kagane and novelfull series now rest longer without changing the cadence of plain-TLS sites.
Behavior
LATEST_CHAPTER_POLL_BROWSER_COOLDOWN, defaulting to 6h.Implementation
README.md,.env.example,backend/AGENTS.md, anddocker-compose.yml.Review findings addressed
The first review found that configuration parsing was correct but
startLatestPollerdid not passBrowserCooldownintolatest.Poller; every browser-backed row would therefore have been due immediately. Production construction now goes throughnewLatestPoller, with a regression test covering both cooldown fields.The review also identified duplicated browser-site knowledge in fetch routing.
slices.Contains(browserBackedSites, site)now reuses the same list already supplied to the store query.Verification
go test ./internal/latest ./internal/store ..go test ./....graphify update .completed.