Frun1na opened a new issue, #5076:
URL: https://github.com/apache/rocketmq-dashboard/issues/5076
### Before creating
- [x] I have searched the existing issues and found no duplicate.
- [x] I have checked the latest `rocketmq-studio` branch where this problem
still exists.
### Bug report
**Which page or component**
Broker cluster topology page → NameServer tab
(`web/src/pages/studio/BrokerCluster.tsx`).
**What happened**
The NameServer table shows a "Connections" (连接数) column, but the value is
hardcoded to `0` in `mapClusters()`:
```ts
nameServers.push({
...
connections: 0,
});
```
The server contract `NameServerInfo` (`web/src/api/cluster.ts`, backed by
the studio cluster API) exposes only `addr` and `status` for a NameServer —
there is no connection count to show. So every NameServer renders "Connections:
0", which reads like a real measurement saying no client is connected. The CSV
export repeats the fabricated value.
**Expected behaviour**
A value that the backend does not provide should not be rendered as a zero
measurement (same principle as #4902, which replaced fabricated zero offsets
with the unknown sentinel). Drop the column (and its CSV field) until the API
actually reports NameServer connections; the Proxy tab keeps its real
`connections` column.
**Environment**
- RocketMQ Studio: upstream `rocketmq-studio` tip `a562601d`
- Browser: any
**Fix PR**
- #5075
--
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]
