RockteMQ-AI commented on issue #4699: URL: https://github.com/apache/rocketmq-dashboard/issues/4699#issuecomment-5756677166
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The issue is well-documented with clear code references. The `loadConfig` failure path in the cluster/ops page sets `clusterInfoList` to `undefined`, which triggers the "unsupported cluster" banner with no retry mechanism. **Root Cause:** When `loadConfig` throws (e.g., network error, corrupted config), the catch block leaves `clusterInfoList` undefined. The render logic interprets `undefined` as "unsupported cluster type" rather than "config load failed". **Impact:** Users see a misleading "unsupported cluster" banner instead of a meaningful error with retry option. Config recovery requires page refresh or navigation away and back. **Severity:** Medium — UX issue, does not affect core messaging functionality. **Suggested Fix:** 1. Initialize `clusterInfoList` to `[]` (empty array) instead of `undefined` on error 2. Add a `configLoadError` state to distinguish "load failed" from "unsupported cluster" 3. Show a retry button when config loading fails PR #4698 addresses this. Reviewers may want to check the fix covers the `undefined` → falsy rendering path. --- *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]
