pilichoumao opened a new issue, #6406: URL: https://github.com/apache/rocketmq-dashboard/issues/6406
### Describe the bug On `rocketmq-studio` at 779b8c0e7aed2396d3cc72743dcd544ea48e9ae6, the Clients diagnostics treat missing protocol/version/language metadata as an additional observed dimension. A direct consumer with `protocol: Remoting, version: V5_0_0` alongside a Proxy consumer with `protocol: null, version: null` gets mixed-protocol and mixed-version warnings, although the Proxy metadata is unknown. These absent fields are intentional in `RocketMQClientProvider.toConnectionVO`. An incomplete consumer scan returning one client (`partial: true`) also raises “Consumer Group only has one online instance”. It cannot establish that no other client is online. The existing partial warning describes only Producer topic scans although the provider also marks incomplete Consumer queries. ### Reproduction and expected behavior Feed these provider-shaped results through `analyzeClientConnections` and render the Clients page. Five new regression cases fail on the current baseline; a temporary prototype passes all 38 relevant existing/new utility and page tests with one worker. Service fixtures model the provider fields; no live Broker/Proxy was used. Keep unknown metadata and partial-scan warnings visible, but only use reported dimensions for mixed-resource warnings and counts. Only assert a single online consumer when the scan is complete. Genuine mixed dimensions, custom reported metadata and complete single-consumer scans must retain their diagnostics. ### Related work #6112 addresses the Java Producer-specific summary, not this `/clients` utility or Consumer inference. #5570 localizes these diagnostics; #5960 propagates subscription inventory failures into partial results. This fix should preserve their scope rather than reproduce them. -- 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]
