youngkermit8-coder opened a new issue, #1945: URL: https://github.com/apache/rocketmq-dashboard/issues/1945
## Bug `RocketMQDashboardProvider` marks a cluster as warning when the Broker topic-config response is null, but the equivalent subscription-group path only handles exceptions. If `getAllSubscriptionGroup` returns a null wrapper or a wrapper with a null table, the dashboard silently reports zero groups and leaves the cluster healthy. This contradicts the unavailable-count behavior introduced by #1683: absence of Broker count data must not be presented as a successful zero. ## Expected behavior - Mark the affected cluster group count as unavailable when the wrapper or its table is null. - Keep the displayed count at zero because no data was returned. - Report the cluster as warning and exclude it from healthy-cluster totals. - Preserve the existing behavior for a valid empty group table. ## Proposed regression coverage Add focused cases for a null wrapper, a null group table, and a valid empty table. ## Duplicate check Searched issues and PRs for null subscription-group responses, unavailable group counts, and dashboard health. #1683 introduced the intended warning behavior but does not cover null responses; no open contribution fixes this exact path. -- 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]
