pilichoumao opened a new pull request, #6315: URL: https://github.com/apache/rocketmq-dashboard/pull/6315
Fixes #6314. The stdio MCP bridge rounds integer request parameters when decoding SDK `JSONRPCRequest.Params` into `float64`. For `rmq.message.query_by_offset`, offset `9007199254740993` reaches Studio as `9007199254740992`; `9223372036854775807` becomes `9223372036854776000` and exceeds Java long range. Decode request params with `UseNumber` before forwarding. This preserves nested numeric literals through instance binding and the actual HTTP transport. Request IDs, notifications and reconnect policy retain their existing behavior. Document the request-param boundary. Validation on rocketmq-studio `5e4c39b053c35a5598cc79ff331b8a54e649d7b1`: - New HTTP wire regression fails on the baseline for both large offsets and passes after the fix; small offset 42 is a control. - Nested values, fractional/exponent numbers, booleans, null, strings, normal numeric/string request IDs, and rejection of trailing/invalid JSON are covered. - `go test -race -count=1 -parallel 1 ./...` passes. - `make fmt vet build-all` passes, including catalog consistency and six target builds/license manifests. Checks ran sequentially with `GOMAXPROCS=1`, `GOMEMLIMIT=384MiB`, `GOFLAGS=-p=1`. No broker or database was needed: the bug is in the outbound bridge encoding. AI-assisted implementation; final diff and regression evidence reviewed. -- 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]
