RockteMQ-AI commented on issue #4465: URL: https://github.com/apache/rocketmq-dashboard/issues/4465#issuecomment-5700663276
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** The Topic and Consumer tables retain selected row keys in component state when the visible result scope changes (search, filter, pagination, or instance switch). The batch-delete action references stale selection state that includes rows no longer visible to the user. **Impact:** For Topic page, confirming batch deletion after an instance switch sends topic names from the previous instance together with the new instance ID — a data integrity risk. For both pages, the batch-delete count misleads the user. **Severity:** Medium-High — can cause unintended resource deletion when combined with instance switching. **Suggested Fix:** Reset the table selection state (`selectedRowKeys`) whenever the query scope changes: instance, search term, type/mode filter, page number, or page size. This is a straightforward frontend state management fix in the Topic and Consumer table components. An automated fix proposal can be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by github-manager* -- 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]
