RockteMQ-AI commented on issue #1708: URL: https://github.com/apache/rocketmq-dashboard/issues/1708#issuecomment-5251749562
**Issue Evaluation** Category: `type/bug` (frontend) | Severity: **Medium** | Status: **Confirmed** The Client Connections page retry mechanism has a state management gap: when `listConnections()` fails but `listInstances()` succeeds, the retry button only resets the instance-load key without re-triggering `listConnections()` for the currently selected instance. The selected instance ID remains unchanged, so the connection effect does not re-run, leaving the page in an empty/error state. **Root Cause:** The retry state does not distinguish between instance-discovery failures and runtime-connection failures. The retry action needs to target the specific failed operation. **Impact:** Users cannot recover from transient connection query failures without navigating away and back. **Proposed Scope:** Focused fix on the retry state logic in the Client Connections page, with targeted frontend tests. This is well-scoped and actionable. This is a valid bug. A fix PR is welcome. --- *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]
