Frun1na opened a new issue, #4932:
URL: https://github.com/apache/rocketmq-dashboard/issues/4932

   ### Before Creating the Bug Report
   
   - [x] I have searched the [open 
issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository 
and believe that this is not a duplicate.
   - [x] This is a defect in RocketMQ Studio, not a usage question and not a 
defect in another Apache RocketMQ repository.
   - [x] I can reproduce this on the current `master` branch, or I have stated 
the exact version I am running below.
   
   ### Studio Version
   
   branch: `rocketmq-studio`
   git commit id: `1ef5d860` (upstream tip at the time of the report)
   deployed as: built from source
   
   ### Runtime Environment
   
   Verified by code tracing and unit tests on `rocketmq-studio` @ `1ef5d860` 
(vitest for `web/`, JUnit for `server/`), not against a specific browser or 
deployment.
   
   ### Connected RocketMQ Cluster
   
   Not cluster-specific: the defect lives in the code path and reproduces on 
any deployment where the trigger condition below holds.
   
   ### Describe the Bug
   
   After archiving or deleting the only conversation on the final page, 
`reload()` refetches the now-empty page and the list shows a blank page with 
the pager stuck on the stale page number.
   
   ### Steps to Reproduce
   
   1. Keep 16 conversations (page size 15) so page 2 holds one row.
   2. Archive or delete that row from the history modal.
   3. The list reloads page 2: an empty list with total 15, stuck on page 2.
   
   ### What Did You Expect to See?
   
   The list clamps back to the last valid page and shows rows.
   
   ### What Did You See Instead?
   
   A blank page until the user manually clicks back to page 1.
   


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