zmuxuny opened a new issue, #6628: URL: https://github.com/apache/rocketmq-dashboard/issues/6628
### 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 rocketmq-studio @ 779b8c0e7aed2396d3cc72743dcd544ea48e9ae6 ### Runtime Environment Linux x86_64; real BrokerCluster React component rendered under the project Vitest/jsdom environment. ### Connected RocketMQ Cluster Two controlled Studio instance fixtures with different Broker, NameServer and Proxy topology. Deferred service responses, no live cluster incident claimed. ### Build Toolchain Project npm lockfile; Vitest and React Testing Library. ### Describe the Bug Switching Broker Cluster from instance A to instance B changes the selector immediately but retains A's completed Broker, NameServer and Proxy rows while B loads. The export button stays enabled outside the loading overlay and downloads A's actual topology CSV under the B selection. ### Steps to Reproduce 1. Open Broker Cluster and let instance A finish loading. 2. Select instance B while deferring B's topology response. 3. Inspect each of the Broker, NameServer and Proxy tabs, then click Export. 4. Resolve B and verify its new data renders and exports correctly. Real-component regression: three tab-specific cases fail all nine target assertions on unchanged production (old rows visible, export enabled, actual old-node CSV emitted). Same-instance and completed-request controls pass. ### What Did You Expect to See? Do not display or export another instance's topology during a scope change. Preserve same-instance refresh behavior and existing request guards. ### What Did You See Instead? A's topology remains visible and exportable while the instance selector says B; after B resolves, its data correctly replaces A. ### Additional Context Credit to yuluo-yx's earlier report #2151 and closed, unmerged proposals #2156/#2201. The load-failure portion was subsequently addressed through #2899/#2904/#2893, but the pending interval remains reproducible on current trunk; #2151 is stale-closed as not planned. Open #5194 fixes request-generation rewind and #5645 changes silent polling errors; this report concerns completed old-scope data retained during a new-scope request, without changing either behavior. Regression command: npx vitest run src/pages/studio/__tests__/BrokerClusterInstanceScope.test.tsx -t "blocks export" --maxWorkers=1 ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
