btlqql opened a new issue, #2430: URL: https://github.com/apache/rocketmq-dashboard/issues/2430
## Problem Several client/group inventory tables use uncontrolled pagination while their search, cluster, namespace, or source filters replace the backing data. If a user is on a later page and narrows the result to fewer pages, the table stays on the old page and appears empty even though matching rows exist on page 1. Confirmed affected views include: - cluster client connections - Studio consumer-group management - LiteTopic inventory/session views ## Reproduction 1. Populate enough rows to navigate to page 3. 2. Apply a search or source filter that leaves only one page of matching data. 3. The table remains on page 3 and displays an empty state. 4. Manually returning to page 1 reveals the matching rows. ## Expected behavior Each table should use controlled pagination and reset or clamp the page when filters, selected cluster/namespace, or refreshed result totals invalidate the current page. ## Suggested validation Add regression tests that navigate to a later page, change each relevant filter/source, and verify matching first-page rows remain visible. Keep the behavior consistent across the affected inventory pages. -- 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]
