pilichoumao opened a new issue, #6314: URL: https://github.com/apache/rocketmq-dashboard/issues/6314
### Before Creating the Bug Report - [x] Searched existing issues and PRs. #5262 fixes REST response decoding; #6136 covers YAML output. Neither fixes MCP request parameters. - [x] Defect in RocketMQ Studio's rmqctl bridge. - [x] Reproduced on current rocketmq-studio. ### Studio Version rocketmq-studio, 5e4c39b053c35a5598cc79ff331b8a54e649d7b1, built from source. ### Runtime Environment macOS, Go CLI tests against an in-process HTTP MCP server; no MySQL or browser needed. ### Connected RocketMQ Cluster No live cluster needed: the defect occurs before the request reaches Studio. The server's MessageQueryByOffsetInput accepts a Java long offset. ### Describe the Bug The MCP bridge decodes JSONRPCRequest.Params (an interface) through json.Unmarshal, converting numbers to float64. Re-encoding the request can change a valid offset or move Long.MAX_VALUE outside the server's accepted range. ### Steps to Reproduce Create a real MCPClientSession against an httptest HTTP endpoint, send tools/call for rmq.message.query_by_offset with offset 9007199254740993, and capture the POST body. Repeat with 9223372036854775807. ### What Did You Expect to See? The HTTP request preserves offset 9007199254740993 / 9223372036854775807 exactly, including after instanceId injection. ### What Did You See Instead? Captured offsets are 9007199254740992 / 9223372036854776000. Small offset 42 is unchanged. ### Additional Context Proposed scope: preserve JSON numbers while decoding client request params; keep existing request IDs, notifications, transport lifecycle and reconnect policy unchanged. Regression tests should capture real outbound HTTP bodies, including nested params and normal JSON values. This is separate from response decoding and mutation preview output precision. ### Are You Willing to Submit a Pull Request? - [x] Yes. -- 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]
