RockteMQ-AI commented on issue #4609: URL: https://github.com/apache/rocketmq-dashboard/issues/4609#issuecomment-5751648303
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The bug is confirmed. Both `openNameServerConfigDiff` and `openBrokerConfigDiff` in `web/src/pages/cluster/index.tsx:373-425` catch failed requests by only resetting `loading: false` while leaving `result: null`. The modal render branches (`:960`, `:1120`) have only two paths: `result` truthy (show diff) or otherwise (show loading Alert). There is no third "failed" branch. **Root Cause:** The catch handlers at `:391-395` and `:418-422` do not set an error state. The render logic has no error branch, so a failed request is visually indistinguishable from an in-flight one. **Impact:** When a config-diff request fails (most commonly because the target node is unreachable), the modal shows a permanent loading banner with no retry path. The operator must close and re-open the modal. **Severity:** Low-Medium — misleading UX but no data risk; the operator can recover by closing the modal. --- *Automated evaluation by RocketMQ AI Assistant* -- 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]
