You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "yuluo-yx (via GitHub)" <gi...@apache.org> on 2026/08/20 15:59:52 UTC
[I] Distinguish Ops loading failures from unavailable runtime configuration [rocketmq-dashboard]
yuluo-yx opened a new issue, #2452:
URL: https://github.com/apache/rocketmq-dashboard/issues/2452
## Problem
The Ops page initializes configuration availability to false and immediately renders the unsupported warning. Users therefore see a false capability warning while the request is pending, and network failures are permanently presented as unsupported configuration.
## Expected behavior
Track loading, ready, and error states separately. Show the unavailable warning only after a successful response explicitly reports false, and provide a retryable error state for request failures.
## Verification
Add focused UI tests for pending, failed, retry, and explicitly unavailable responses.
--
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: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Distinguish Ops loading failures from unavailable runtime configuration [rocketmq-dashboard]
Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
RockteMQ-AI commented on issue #2452:
URL: https://github.com/apache/rocketmq-dashboard/issues/2452#issuecomment-5358521686
**Issue Evaluation**
Category: `bug` | Status: **Confirmed**
The Ops page initializes configuration availability to `false` and renders the unsupported warning immediately before the async config check completes. This causes:
1. A flash of false "unsupported capability" warning during page load
2. Network failures permanently displayed as "unsupported" rather than "failed to load"
**Root Cause:** No tri-state handling (loading / loaded / failed) for configuration availability — the initial `false` value is indistinguishable from a confirmed "unsupported" result.
**Impact:** Users see misleading warnings during normal page load; network errors are permanently misclassified.
**Severity:** medium
The fix should introduce a loading state and distinguish between "not yet loaded", "confirmed unsupported", and "load failed".
---
*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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Distinguish Ops loading failures from unavailable runtime configuration [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #2452: Distinguish Ops loading failures from unavailable runtime configuration
URL: https://github.com/apache/rocketmq-dashboard/issues/2452
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Distinguish Ops loading failures from unavailable runtime configuration [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #2452:
URL: https://github.com/apache/rocketmq-dashboard/issues/2452#issuecomment-5447728603
This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org