Aias00 opened a new issue, #804: URL: https://github.com/apache/rocketmq-dashboard/issues/804
### Before Creating the Bug Report - [x] I have searched the existing issues and pull requests. ### Runtime platform environment N/A ### RocketMQ version rocketmq-studio branch ### JDK Version N/A ### Describe the Bug `web/src/pages/studio/BrokerCluster.tsx` defines broker, NameServer, and Proxy records directly in the page component. The page renders these hard-coded records instead of loading the current cluster topology through the existing cluster service/API contract. This can mislead users because the Studio control-plane page shows apparently healthy Broker/NameServer/Proxy nodes even when the backend has no such cluster data or the API request fails. ### Steps to Reproduce 1. Start the Studio web UI with real API mode. 2. Open the Broker Cluster page. 3. Observe that rows such as `broker-a`, `nameserver-a`, and `proxy-a` can be rendered from page-local constants rather than from `/api/clusters`. ### What Did You Expect to See? The BrokerCluster page should render data from the existing cluster API/service. If the service is unavailable or returns no nodes, the page should show an empty/error state instead of demo topology. ### What Did You See Instead? The page contains local mock records and renders them directly. ### Additional Context This is in the Studio/control-plane scope: infrastructure topology views should not bypass the Provider/AdminClient-backed service layer. -- 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]
