Follow NWS /alerts/active pagination — alerts beyond page 1 are dropped then falsely cleared #41
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/WeatherBot#41
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
fetch_alerts_for_states(app/services/nws.py:164-180) readsfeaturesfrom asingle response and never follows
pagination.next. In a large multi-stateoutbreak, alerts past page 1 are invisible: no notifications, and existing
SentAlertrows for them are cleared as "disappeared from feed" by_clear_missing_alerts. Loop onpagination.next(bounded, e.g. max 10 pages),accumulate features, and log when pagination occurs so outbreak-scale polls are
observable.
Acceptance criteria:
Filed from the 2026-07-17 codebase audit (
docs/.internal/report-2026-07-17.md), finding F-02.Fixed in #92 (merged to
main).fetch_alerts_for_statesnow followspagination.next(bounded to 10 pages, logged when >1 page) so large multi-state outbreaks aren't truncated to page one and then cleared as "disappeared". Regression test uses a mocked 2-page response asserting both pages' alerts process.