Frun1na opened a new issue, #4597: URL: https://github.com/apache/rocketmq-dashboard/issues/4597
### 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: master git commit id: d50ffecc9d7e8f8f46da64198831bd7952e6974e deployed as: built from source (`cd web && npm run dev`) ### Runtime Environment OS: Windows 11 with WSL2 (Ubuntu 24.04.3 LTS) MySQL: not involved in this frontend issue browser: Chrome 151.0.7922.174 on Windows 11 ### Connected RocketMQ Cluster RocketMQ 4.x / 5.x cluster registered in Studio access mode: Proxy gRPC (PROXY_CLUSTER instance) deployment: any cluster registered in Studio; verified by code inspection and unit tests with mocked services, no specific cluster deployment required ### Build Toolchain _No response_ ### Describe the Bug When switching between instances on the Topic page, the search text, type filter and table page from the previous instance are kept. The page also caches topic routes and consumer pages in `routesByTopic` / `consumersByTopic` keyed by topic name only and never clears them, so a topic with the same name in another instance shows the previous instance's routes and consumer data. Other instance-scoped pages (consumer, message, ACL) already remount their content by the selected instance; the topic page does not. ### Steps to Reproduce 1. Start Studio and open the Topic page for instance A. 2. Search for a topic name (e.g. `topic-01`) in the search box. 3. Switch to instance B with the instance selector. 4. Observe that the search box still contains the old term and the page request is issued with the stale search text; a topic with the same name as one in instance A can show instance A's routes/consumer data. ### What Did You Expect to See? Filters and caches reset when the instance changes, and the page shows instance B's data only. ### What Did You See Instead? The previous instance's search text, type filter and table page persist after switching, and the per-topic route/consumer caches are keyed by topic name only, so cross-instance data can be shown for same-named topics. ### Additional Context Fix proposal: #4594 (remounts the topic page content by the selected instance, mirroring the consumer page). ### 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]
