RockteMQ-AI commented on issue #4489: URL: https://github.com/apache/rocketmq-dashboard/issues/4489#issuecomment-5708980599
**Issue Evaluation** Category: `bug` | Status: **Confirmed** This is a valid regression. The Topic page's mutation state (edit dialog, send-message form, sync target) is not invalidated when the selected instance changes, allowing stale A-instance data to be submitted against B-instance. **Root Cause:** The instance-keyed Topic content remount (previously implemented in #1722 / #2308) was lost, so the component stays mounted across instance switches. The `handleCreate` function reads `selectedInstanceId` at submit time, but the form state was populated from a different instance. **Impact:** Silent misconfiguration — editing topic-a on instance A and then switching to instance B can submit A's form values against B's broker. This is a data integrity risk for users managing multiple instances. **Severity:** High — silent wrong-instance mutation with no user-visible warning. **Proposed scope is appropriate:** Restore the instance-keyed Topic content boundary (matching Consumer/ACL page patterns) without changing Topic APIs or Broker semantics. A PR will be generated to address this. Reply with feedback if the proposed approach needs adjustment. --- *Automated evaluation by @RockteMQ-AI* -- 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]
