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

   ### Before Creating the Bug Report
   
   - [x] Searched `MessageQueryHistoryDrawer` and history pagination reports. 
Open #5156 adds delete/clear actions and only decrements a page after its own 
deletion; it does not clamp a fetched page or change the fixed page-size 
controls.
   
   ### Studio Version
   
   `rocketmq-studio@c99b9ad50b79467546997e51f3401d57ceebea5f`.
   
   ### Describe the Bug
   
   The message/trace history drawer retains its page when the instance changes 
or the history total shrinks between openings. The successful response can have 
no items and a total smaller than the current page, but the drawer never 
re-queries a valid page. Its two tables also let antd show a page-size selector 
when total exceeds 50, although requests always use PAGE_SIZE=20 and onChange 
only stores the page number.
   
   ### Steps to Reproduce
   
   1. Open message or trace history with 60 records and select page 3.
   2. Change the drawer's instance to one with a single history record, or 
shrink the server total and reopen.
   3. The request is still for page 3 and the existing record is hidden behind 
an empty table.
   4. With more than 50 records, the size selector offers sizes the fixed-size 
request does not honor.
   
   ### Expected Behavior
   
   Clamp successful responses to the last valid page (at least 1) and re-query 
that page. Keep the controls consistent with the fixed 20-row page size for 
both tabs.
   
   ### Verification Plan
   
   Component regressions with changing response totals for message and trace 
history, and a fixed-size-control assertion.
   
   ### Are You Willing to Submit a Pull Request?
   
   Yes.


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