youngkermit8-coder opened a new pull request, #1652: URL: https://github.com/apache/rocketmq-dashboard/pull/1652
## Summary - keep a Topic consumer group's aggregate lag at `-1` when any queue lag is unknown - report `-1` when group consume stats cannot be read instead of fabricating zero lag - preserve normal summation when every queue lag is known ## Root cause `ConsumerLagResolver` deliberately returns `-1` for an unknown queue lag, but `getTopicConsumers` added every resolved value directly into `diffTotal`. A known lag of `10` plus one unknown queue therefore became the plausible but incorrect value `9`. The per-group exception fallback also used `0`, which means known zero lag rather than unavailable statistics. The aggregation now propagates the unknown sentinel and only sums fully known queue values. ## Validation - both new regression cases failed on the unmodified implementation (`9` and `0` instead of `-1`) - `RocketMQMetadataProviderTest` + `ConsumerLagResolverTest`: 17/17 passed - all Apache provider tests: 98/98 passed - Checkstyle: 0 violations - `mvn package -DskipTests`: passed - full backend suite: 946/948 passed; the same two `ToolGatewayServiceTest` JSON Schema failures reproduce on the exact clean upstream base `990ba09` Closes #1650 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
