RockteMQ-AI commented on issue #1720: URL: https://github.com/apache/rocketmq-dashboard/issues/1720#issuecomment-5252324705
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** The Topic page (`frontend-new/src/pages/Topic/topic.jsx`) calls `getTopicList()` only once on mount via `useEffect(fn, [])`. There is no reactive instance context in the app — the Ops page manages `selectedNamesrv` in its own local `useState` with no broadcast mechanism. All instance-scoped state (selected topic details, send-message state, import state, cached routes, consumer relationships, open dialogs) persists unchanged when the user switches instances. **Impact:** Users can view or act through stale dialogs/data from a previous instance after switching, leading to incorrect operations or confusion. **Severity:** Medium — functional correctness issue in multi-instance management. **Affected files:** - `frontend-new/src/pages/Topic/topic.jsx` - `frontend-new/src/pages/Ops/ops.jsx` - `frontend-new/src/router/index.jsx` **Suggested fix:** Introduce a shared instance context (or equivalent) with a `useEffect` dependency on the current instance in `topic.jsx` to reset state and re-fetch data on instance changes. An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by github-manager-bot* -- 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]
