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

   ### 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
   
   The DLQ message drawer takes its query window from the live group-level 
导出时间范围 picker. Changing the picker while the drawer is open updates the banner 
but not the loaded rows, while 导出全部 and post-resend reloads use the new window.
   
   ### Steps to Reproduce
   
   1. Open 消息明细 for a group.
   2. Change the top 导出时间范围 picker.
   3. The banner shows the new window, the table still shows the old one, and 
导出全部 downloads the new window.
   
   ### What Did You Expect to See?
   
   Banner text, table rows and export window agree: either the drawer reloads 
or stays pinned to the range it was opened with.
   
   ### What Did You See Instead?
   
   Three different windows are shown at once depending on which part of the UI 
you look at.
   


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