Frun1na opened a new issue, #5646: URL: https://github.com/apache/rocketmq-dashboard/issues/5646
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version branch: `rocketmq-studio` git commit id: `6a68042f` deployed as: built from source ### Runtime Environment OS: Ubuntu 22.04 (WSL2) MySQL: not applicable — the defect is in the NameServer table's rendering, covered by the component test browser: not needed; reproduced with the page's own component test (`web/src/pages/studio/__tests__/BrokerCluster.test.tsx`) ### Connected RocketMQ Cluster RocketMQ version: not applicable — mock mode serves the fixture cluster access mode: not applicable deployment: not applicable ### Describe the Bug The NameServer registry table on the cluster topology page (`web/src/pages/studio/BrokerCluster.tsx`) shows a "Connections" column whose value is not a measurement: the page hardcodes `connections: 0` for every row when it maps the API response, because the cluster API's `NameServerInfo` carries only `addr` and `status`. An operator reading the table sees "0" for every NameServer and can only conclude that no client is connected to any NameServer — a fabricated zero presented as a measurement. The same fabricated column is written into the NameServer CSV export. (The Proxy table is unaffected: `ProxyInfo` really does carry `connections`, so its column reports a real number.) ### Steps to Reproduce 1. Open the cluster topology page for an instance and switch to the NameServer tab. 2. Look at the Connections column: it shows 0 for every NameServer, in every environment, because the value never comes from the API. 3. Export the NameServer table: the CSV carries the same `Connections` column. ### What Did You Expect to See? No Connections column for NameServers — the column should only exist where the API actually provides the number, as it does for proxies. (Showing the count would need a new server-side field, which is a separate change.) ### What Did You See Instead? A `connections: 0` column rendered for every NameServer row and included in the CSV export, indistinguishable from a real measured zero. ### Additional Context - hardcoded value: the NameServer mapping in `web/src/pages/studio/BrokerCluster.tsx` (`mapClusters`) sets `connections: 0`; the local `NameServerRecord` type and the CSV column list carry it forward. - API shape: `web/src/api/cluster.ts`, `NameServerInfo` has `addr` and `status` only. ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. --- Re-submission: the original report (#5076) was closed by the stale bot after 7 days without triage activity, and GitHub now rejects reopening items in this repository. Refiled unchanged; the fix PR is linked below. -- 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]
