Loyal-Young opened a new issue, #6047:
URL: https://github.com/apache/rocketmq-dashboard/issues/6047

   ### Before Creating the Bug Report
   
   - [x] Searched open issues and PRs for ResourceOperationTimelineDrawer and 
pagination. #5608 explicitly leaves this drawer for follow-up; #5636 handles 
system alerts.
   
   ### Studio Version
   
   rocketmq-studio at 29fe48abc98583cfc77f97188f187cca3ad85dae.
   
   ### Runtime Environment
   
   Windows / Node 24.18.0, frontend with controlled audit API responses; no 
live broker needed.
   
   ### Connected RocketMQ Cluster
   
   Not required for the audit drawer pagination.
   
   ### Describe the Bug
   
   ResourceOperationTimelineDrawer stores an empty out-of-range page after 
audit retention/cleanup shrinks the result total. Its pagination is only 
rendered when records.length > 0, so the operator cannot even navigate back 
from that empty view.
   
   ### Steps to Reproduce
   
   1. Open a resource timeline containing 21 records and navigate to page 2 (20 
per page).
   2. Before that request returns, retention leaves only 5 matching records.
   3. Respond with items: [], total: 5.
   4. The drawer displays Empty and removes the pager, despite records still 
being available on page 1.
   
   ### What Did You Expect to See?
   
   Clamp to the last valid page and re-query with the same resource/date scope; 
total zero should settle on page 1 without a loop.
   
   ### Additional Context
   
   The query-key ownership guard already protects resource changes. The fix 
should preserve it and keep valid page navigation working.
   
   ### Are You Willing to Submit a Pull Request?
   
   Yes, including interaction tests for shrinking totals and normal navigation.
   
   ### AI assistance
   
   AI assistance was used for source inspection and drafting; deterministic 
verification will be recorded with the PR.


-- 
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]

Reply via email to