The GitHub Actions job "CI" on rocketmq-dashboard.git/rocketmq-studio has 
failed.
Run started by GitHub user lizhimins (triggered by lizhimins).

Head commit for run:
fb6455a0352e7431144eb355ea66f1000b7fbc55 / 0 <[email protected]>
fix(consumer): keep an unknown total lag from being a partial subtotal (#7053)

When the queue scan did not cover every queue, analyzeConsumerGroupHealth fell 
back
to the sum of the queues it did see and reported that subtotal as the group's 
total
lag - a partial measurement presented as a complete one. reportedLag now yields 
null
unless every queue in the progress list had a readable lag, and the single 
render
site already treats null as unknown. The health-issue path keeps using the known
subtotal (summaryReportedLag ?? totalKnownLag), so this changes only what is
reported as the total, not which issues are raised.

This complements rather than duplicates the delay-availability work that landed 
in
#5918: that change covers delaySeconds, which has no sentinel and needs a 
boolean
flag, while totalLag already carries the -1 sentinel, so a single isLagAvailable
conversion at the boundary is enough. The test file conflicted with those 
additions;
both sides' cases are kept.

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

With regards,
GitHub Actions via GitBox

Reply via email to