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

   ### 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
   
   With 自动刷新 enabled, every failed background tick pops an error toast. The 
page already treats silent background refreshes quietly for the diagnostics 
modal, but the main list error path ignores its `silent` flag.
   
   ### Steps to Reproduce
   
   1. Open the consumer group page and enable 自动刷新.
   2. Make the list endpoint fail (restart the server or block the broker).
   3. A new error toast appears every 2 seconds until the request succeeds or 
auto-refresh is disabled.
   
   ### What Did You Expect to See?
   
   A failed silent background tick updates state without toasting; only 
user-initiated loads surface a toast.
   
   ### What Did You See Instead?
   
   An unbounded toast storm that also pushes real errors off the screen.
   


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