zmuxuny opened a new pull request, #6653:
URL: https://github.com/apache/rocketmq-dashboard/pull/6653

   ### Which Issue(s) This PR Fixes
   
   Fixes #6628.
   
   ### Brief Description
   
   Clear completed Broker/NameServer/Proxy snapshots when the selected instance 
scope changes, preventing old-instance rows and CSV exports while the new 
instance is loading. Preserve same-instance refresh and existing request guards.
   
   Credit to yuluo-yx's earlier report #2151 and closed, unmerged proposals 
#2156/#2201. The pending-scope interval remains reproducible after the 
load-failure work in #2899/#2904/#2893. This does not replace #5194's 
generation guard or #5645's polling-error work.
   
   ### Verification
   
   Base: rocketmq-studio@779b8c0e7aed2396d3cc72743dcd544ea48e9ae6.
   
   The following validation was completed on October 13, 2026 against the 
prepared source. The fork head and tree were rechecked on October 14; these 
tests are not claimed as a fresh rerun.
   
   26 focused tests passed; an independent 10-test rerun passed. A separate 
compatibility check with #6348 passed 27 tests. Full frontend run: 1,612 tests 
in 159 files passed. Real component regressions cover all three topology tabs, 
disabled export during the scope transition and completed-request controls.
   
   TypeScript/production build and artifact-license checks passed. Lint 
reported zero errors and ten existing warnings. Local tests used Node 24, while 
CI uses Node 20. Browser visual QA and a live cluster are not claimed.
   
   Independent source/test review completed. AI assistance was used for 
implementation and regression authoring. Controlled fixtures were used; no live 
production incident, deployment or broker mutation is claimed. Upstream CI for 
this new PR remains to be verified.
   


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