unbridled-41 opened a new issue, #5947:
URL: https://github.com/apache/rocketmq-dashboard/issues/5947
### Studio Version
branch: `rocketmq-studio` @ `7e7aa344` (the revision verified; the branch is
based on it)
deployed as: not required to reproduce
### Runtime Environment
Reproduced with the frontend tests (`cd web && npx vitest run
src/pages/studio/__tests__/BrokerCluster.test.tsx`).
### Connected RocketMQ Cluster
Any cluster; the mock/demo mode shows the problem immediately, a real
deployment shows a blank column.
### Describe the Bug
`mapClusters` copies the cluster-level version into the per-node rows:
```ts
nameServers.push({ ..., version: cluster.version, ... });
proxies.push({ ..., version: cluster.version, ... });
```
but neither `NameServerVO` nor `ProxyVO` carries a version -
`NameServerInfo` is `{addr, status}` and `ProxyInfo` is `{addr, status,
connections, grpcPort, remotingPort}` in `docs/api-spec.md` and in
`web/src/api/cluster.ts` - and the cluster's own version is not set on the
discovery path either (`RocketMQClusterProvider.buildClusterVO` sets
name/type/status/brokers/proxies/nameServers/tpsHistory/counts only). So the 版本
column showed the mock's cluster version for every node in demo mode and a
blank cell in production, and both tabs exported that value as a `Version` CSV
column.
### Steps to Reproduce
1. Open 集群管理 → NameServer 管理 (or Proxy 管理) in demo mode: every row shows the
cluster's version (`5.3.0`) as its own.
2. Against a real cluster the same column is blank.
### What Did You Expect to See?
A column that reports something the API actually provides, or no column.
### What Did You See Instead?
A fabricated value in demo mode and an empty one in production, in the table
and in the exported CSV.
### Evidence
- `web/src/pages/studio/BrokerCluster.tsx` (`mapClusters`, the two columns,
`NAMESERVER_EXPORT_COLUMNS`/`PROXY_EXPORT_COLUMNS`), `web/src/api/cluster.ts`,
`docs/api-spec.md` (`NameServerInfo`, `ProxyInfo`),
`server/.../provider/apache/RocketMQClusterProvider.java`.
- `cd web && npx vitest run
src/pages/studio/__tests__/BrokerCluster.test.tsx -t 'Version column'` - fails
before the fix.
### Impact
Version-specific troubleshooting reads a value that belongs to the cluster
(or nothing at all), and the exported topology CSV carries it as the node's
version.
### Acceptance Criteria
- The NameServer and Proxy tables (and their CSV exports) no longer present
the cluster version as the node's, while the Broker tab keeps its own
`BrokerVO.version`, with a regression test.
**Corresponding PR:** #ISSUEPR#
--
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]
