You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by GitBox <gi...@apache.org> on 2026/10/19 17:40:22 UTC
[GH] (rocketmq-dashboard/fix/btl-client-connected-at): Workflow run "CI" failed!
The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/btl-client-connected-at has failed.
Run started by GitHub user btlqql (triggered by btlqql).
Head commit for run:
2ad0d26f51c786f9b1af21308c03dcd07fa8da59 / btlqql <29...@qq.com>
fix(web): drop the client heartbeat column the API can never fill (#6086)
The clients page advertised a connection time in three places -- the table's
`Heartbeat` column, the CSV export's `Connected At` column and the connection detail
dialog -- all bound to `ClientConnectionVO.connectedAt`, a field no provider ever
assigns. `RocketMQClientProvider.toConnectionVO(ProducerInfo, ...)` (`:337`) and
`toConnectionVO(Connection, ...)` (`:469`) build the VO from `ProducerInfo` /
`Connection` payloads that carry no timestamp, and the proxy branch passes none
either, so every cell rendered `-`. That reads as "this client never sent a
heartbeat" rather than "this build does not collect it".
Drop the three surfaces instead of inventing a timestamp the brokers do not report --
the same resolution #5600 took for the fabricated NameServer `Connections` column.
The regression test asserts that the column header, the dialog row and the CSV column
are all gone, and the existing CSV/dialog expectations are trimmed accordingly.
Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/39283508837
With regards,
GitHub Actions via GitBox