unbridled-41 opened a new issue, #5474: URL: https://github.com/apache/rocketmq-dashboard/issues/5474
### Studio Version branch: `rocketmq-studio` @ `6a68042f` (the revision verified; the branch is based on it) deployed as: built from source (unit test) ### Runtime Environment Not environment-specific: frontend scan scope. ### Connected RocketMQ Cluster Any instance whose topic inventory exceeds one page, or where a search/type filter is active. ### Describe the Bug `openSyncModal` checks the routes of the topics currently listed — the current server page, under the active search/type filter — and then reports the result as an inventory-wide verdict: "所有 Topic 在 Broker 上均有路由，无需同步。" A topic that is missing its route on another page is therefore declared healthy and cannot be synced from the dialog, which is the dialog's only purpose. ### Steps to Reproduce 1. Open the topic page on an instance with more than one page of topics. 2. Click 同步数据 and read the verdict. 3. Compare with the pagination total: the check only examined the rows on screen. ### What Did You Expect to See? The verdict states what was scanned (the number of topics, and that the scope is the current page and filter), or the scan covers the inventory. ### What Did You See Instead? "所有 Topic 在 Broker 上均有路由" after checking one page. ### Evidence - `web/src/pages/instance/topic.tsx` (`openSyncModal` iterating `topics`, the empty-state copy). - `cd web && npx vitest run src/pages/instance/__tests__/TopicPage.test.tsx` — the existing sync case now asserts the scope note and fails before the change (`Unable to find an element with the text: /当前列表中的 1 个 Topic 在 Broker 上均有路由.*只覆盖当前页与当前筛选/`) and passes after (`Tests 34 passed`). ### Impact A maintenance action reports a scope it did not check and hides the topics it exists to find. ### Acceptance Criteria - The verdict states the scanned scope (or the scan becomes inventory-wide). - A test pins the wording/scope. **Corresponding PR:** #5444 -- 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]
