The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/topic-consumer-unknown-lag has failed. Run started by GitHub user lizhimins (triggered by lizhimins).
Head commit for run: 698747e9870fb77506c7c28174d5fc1d82a584bd / wang1r <[email protected]> fix(web): show an unresolvable topic consumer lag as unavailable The topic detail consumer list only treated metricsAvailable === false as "no number". The backend has a second way of saying that: when the broker returns ConsumeStats but a queue offset cannot be resolved, RocketMQMetadataProvider sets diffTotal to ConsumerLagResolver.UNKNOWN (-1) and leaves metricsAvailable true, because stats really were returned. That row rendered as a backlog of -1, which reads as a negative lag. The consumer page's queue column already routes the same field through isLagAvailable and prints the unavailable label, so the two pages disagreed about the same sentinel. Reuse that guard here. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/36845662377 With regards, GitHub Actions via GitBox
