zjncs opened a new issue, #5635:
URL: https://github.com/apache/rocketmq-dashboard/issues/5635
## Description
The repo has an established convention for paginated lists — when a page
query returns `items.length === 0 && total > 0 && page > 1`, the page is reset
to the last valid page and re-queried (alerts.tsx:375-381 documents it as
deliberate policy). Eight pages implement it: alerts, audit, acl,
UserManagement, topic, consumer, settings/DataSourceTab,
settings/CloudCredentialTab.
`systemAlerts.tsx`'s main list is missing it (its own silences drawer even
handles delete-on-last-page). System alerts expire / are reaped server-side, so
the feed shrinks under the user: anyone paging to a now-out-of-range page gets
a **permanently empty list** while the pagination still shows the old total —
the view reads as "no alerts" and never self-recovers.
Failing test on master (deterministic): page 1 shows total 25; clicking page
2 returns `{items: [], total: 20}` — no clamp refetch is fired.
## Expected behavior
Apply the same clamp as the other 8 pages: re-query the last valid page
instead of storing the empty result.
## Environment
- branch: master (0228dad5)
- file: `web/src/pages/ops/systemAlerts.tsx` (load effect at ~200-220)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
