X-LightYear opened a new pull request, #5109: URL: https://github.com/apache/rocketmq-dashboard/pull/5109
## Summary - include LiteTopic lag rows in Aliyun consumer-group progress results - preserve the existing topic-level lag and unknown-offset semantics - add deterministic regression coverage for a LiteTopic-only lag response ## Problem Aliyun `GetConsumerGroupLag` returns LiteTopic backlog in `data.liteTopicLagMap`, but Studio only converted `data.topicLagMap`. A consumer group consuming only LiteTopics therefore returned an empty progress result despite the API providing a valid lag measurement. ## Root cause `AliyunInstanceProvider.getGroupProgress` delegates the response to `AliyunConverters.toQueueProgressRows`, which iterated only the ordinary topic lag map and ignored the separate LiteTopic lag map. ## Fix Convert both ordinary topic and LiteTopic lag entries through the same topic-level progress-row path. The existing unknown offset sentinel is retained because the Aliyun API exposes topic-level lag rather than broker queue offsets. Aggregate fallback behavior is unchanged. Fixes #5108 ## Testing - `AliyunConvertersLagTest`, `AliyunInstanceProviderTest`: 42 passed - related converter/provider/metadata/MCP tests: 104 passed - checkstyle: 0 violations - backend package and Spring Boot repackage: passed with `-Dmaven.antrun.skip=true` because this environment has no `python3` for the existing license gate ## Scope No frontend, schema, or unrelated provider behavior was changed. -- 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]
