btlqql opened a new issue, #2219: URL: https://github.com/apache/rocketmq-dashboard/issues/2219
## Problem `RealClusterProvider` assumes every NameServer topology entry is fully populated. A partial response containing a null cluster name, null broker-name set, null broker entry, or null fallback address can currently fail discovery with a runtime exception. One malformed entry then hides otherwise valid clusters from Studio. ## Reproduction Pass a `ClusterInfo` containing a valid cluster alongside a null cluster entry or a broker-name set containing null/missing brokers to `describeClusters`. The mapping pipeline dereferences or sorts the malformed value instead of retaining the valid topology. ## Expected behavior Discovery should skip malformed topology entries, preserve valid clusters and brokers, and return an empty result when the response contains no valid broker topology. ## Proposed approach Filter invalid cluster and broker entries at the NameServer response boundary, including null fallback addresses, and cover mixed-validity and all-invalid responses with focused unit tests. I searched issues and pull requests across all states for the provider path and malformed/null topology behavior. I did not find an existing implementation. -- 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]
