unbridled-41 opened a new issue, #5473: URL: https://github.com/apache/rocketmq-dashboard/issues/5473
### 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 selection state. ### Connected RocketMQ Cluster Not cluster-specific. ### Describe the Bug Deleting a topic through its own row action reloads the page but never prunes `selectedRowKeys`. A checked row that disappears keeps the batch delete armed with a name that no longer exists: every later click re-submits it, the server rejects the delete, and the failure path re-seeds exactly that selection — so the button stays stuck with no visible row to uncheck. The sibling consumer page already prunes the deleted name from the selection. ### Steps to Reproduce 1. Check a topic's checkbox. 2. Delete that topic from its row action (the row disappears). 3. Click the remaining "删除 (1)" button: it fails with "1 个 Topic 删除失败" and the selection comes back. ### What Did You Expect to See? The selection is reconciled with the rows that still exist. ### What Did You See Instead? A permanently armed batch action that can only fail, with nothing on screen to clear it. ### Evidence - `web/src/pages/instance/topic.tsx` (the single-delete handler; the batch button and its failure path), `web/src/pages/instance/consumer.tsx` (the precedent that prunes). - `cd web && npx vitest run src/pages/instance/__tests__/TopicPage.test.tsx` — the added case fails before the change (the "删除 (1)" button survives the row's deletion) and passes after (`Tests 35 passed`). ### Impact A stuck batch action that cannot succeed and cannot be cleared from the UI. ### Acceptance Criteria - A deleted row's key is dropped from the selection. - A regression test pins the button's disappearance. Related: #2427 (the same invariant — selection reconciled with the current result — reported for the instance inventory). **Corresponding PR:** #5443 -- 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]
