The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/lite-topic-cross-master-aggregation has failed. Run started by GitHub user zjncs (triggered by zjncs).
Head commit for run: edd396325bcba860ae7f93da12030e96f0cd5c25 / zjncs <[email protected]> fix(lite-topic): sum lite topic count and backlog across every reporting master discoverParentTopics already unions groups across masters because a parent topic can be sharded across brokers, but buildSummary kept reading the parent's lite topic count and each group's lag from a single brokerAddr — the one the accumulator happened to overwrite last. On a sharded parent every other master's lite topics and lag were invisible: a parent split across two brokers with 2+3 lite topics reported 3, and a group holding lag 7+5 across them reported 5. The accumulator now tracks every master that reported the parent and, per group, the masters that reported the group; buildSummary sums the per-master parentTopicInfo counts and the per-master group lag over exactly those masters, so an unsharded parent still reads from the single master that reported it. Signed-off-by: zjncs <[email protected]> Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/37189012300 With regards, GitHub Actions via GitBox
