X-LightYear opened a new pull request, #7272: URL: https://github.com/apache/rocketmq-dashboard/pull/7272
## Problem The `rmq.litetopic.extend_ttl` MCP mutation reports the requested TTL after execution, even though the Apache provider applies broker normalization. ## Reproduction 1. Use an Apache instance with a registered LiteTopic parent such as `orders`. 2. Execute `rmq.litetopic.extend_ttl` with `newTtlMillis = 2678400000` (31 days). 3. Inspect the returned `result.newTtlMillis`. ## Expected behavior The result should report the effective broker TTL: 30 days (`2592000000` ms). The provider rounds to whole minutes and clamps the value to the broker''s 30-day maximum, as already described by the tool preview and catalog. ## Actual behavior The handler returns the original requested value, 31 days, although the provider writes 30 days. The MCP result therefore describes a state that differs from the state applied to the broker. ## Root cause `LiteTopicExtendTtlToolHandler.execute` delegated the request and then echoed `input.newTtlMillis()` without applying the same minute-rounding and 30-day cap used by `RocketMQLiteTopicProvider`. ## Fix Report the effective normalized TTL while preserving the original request sent to the service. ## Testing - pre-fix deterministic regression failed: expected `2592000000`, received `2678400000` - post-fix handler, service, and provider tests: 42 passed - Checkstyle: 0 violations - `git diff --check`: passed Fixes #7271 -- 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]
