123123213weqw opened a new pull request, #7342: URL: https://github.com/apache/rocketmq-dashboard/pull/7342
Fixes #7271. `rmq.litetopic.extend_ttl` reported the requested TTL after execution even though the Apache provider applies broker normalization — a 31-day request echoed `2678400000` in the result while the broker actually held the 30-day maximum (`2592000000`), so the MCP result described a state that differed from the applied one. The handler now computes the applied value through `appliedTtlMillis`, mirroring the provider's normalization exactly (whole-minute granularity, minimum one minute, clamped to the 30-day maximum), and the output's `newTtlMillis` reports that effective state — while the original request is still what reaches `LiteTopicService.extendTTL`, and the preview's granularity/cap warnings keep describing the requested value. Red-first: two regression tests (rounded-to-minutes and clamped-at-30-days) fail on the old code echoing the raw request and pass asserting the effective value. Handler suite 6/6; neighbor suites (schema contract + litetopic family) 39/39. -- 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]
