123123213weqw opened a new pull request, #5725: URL: https://github.com/apache/rocketmq-dashboard/pull/5725
## What is the purpose of the change The LiteTopic session detail API and the `rmq.litetopic.session` tool never return `popProgress`: `LiteTopicService.toSessionVO` does not map it, so the field that `LiteTopicSessionVO`, the tool output contract and the page all declare is always absent. The LiteTopic page renders its "Pop 进度" progress section only when `popProgress` is non-null (`web/src/pages/studio/LiteTopic.tsx`), so real deployments never show the section at all. The value last existed in the pre-provider stub (`totalMessages=5000, consumedMessages=4800, popProgress=96`), i.e. the pop consumption progress percent — the same integer-percent contract #583 fixed the page to render directly. ## Brief changelog - Map the session's pop consumption progress percent (`LiteTopicSession.getConsumptionProgress()`, rounded) into `LiteTopicSessionVO.popProgress` in `toSessionVO`. - Leave the field absent when the message counters are unknown, so the page hides the section instead of showing a fabricated 0%. ## Verifying Red-first: `LiteTopicServiceTest.getSessionShouldCarryPopProgressWhenCountersAreKnown` fails on `rocketmq-studio` (expected 96, got null) and passes with the change; `getSessionShouldLeavePopProgressAbsentWhenCountersAreUnknown` pins the absent case. `mvn test -Dtest='LiteTopicServiceTest,LiteTopicControllerTest,LiteTopicSessionToolHandlerTest'` is green (24 tests). -- 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]
