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/02 03:21:21 UTC

[GH] (rocketmq-dashboard/fix/btl-aliyun-litetopic-lag): Workflow run "CI" failed!

The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/btl-aliyun-litetopic-lag has failed.
Run started by GitHub user btlqql (triggered by btlqql).

Head commit for run:
1771d2afe40efb3fa4223f6bd43c4de2a7eee382 / btlqql <29...@qq.com>
fix(alibaba): report LiteTopic lag in Aliyun consumer group progress

AliyunConverters.toQueueProgressRows read only data.topicLagMap, so a
consumer group whose subscriptions are all LiteTopics produced an empty
progress list even though GetConsumerGroupLag returned a valid
liteTopicLagMap with per-LiteTopic ready counts.

Both breakdowns are now converted with the shared topic-level row builder
(the unknown queue-offset sentinel is unchanged), and the aggregate
totalLag fallback still applies only when neither breakdown is present.

Regression: AliyunConvertersLagTest#liteTopicLagShouldProduceAProgressRowTest
and #liteTopicAndTopicBreakdownsShouldBothBeReportedTest fail on the
unmodified tree (empty row list, missing lite-orders row) and pass with the
fix.

Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/36959364155

With regards,
GitHub Actions via GitBox