The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/yy-int64-precision has failed. Run started by GitHub user yyqdbngt (triggered by yyqdbngt).
Head commit for run: 9157b4606e660a1d8569ed7507054aedd12eb0be / yyqdbngt <[email protected]> fix(rmqctl): keep int64 values beyond 2^53 exact in Studio output The Studio response payload is decoded into the caller's any, and encoding/json turns every JSON number inside an any into a float64, so an int64 field such as a RocketMQ offset silently lost precision above 2^53 (9007199254740993 printed as 9007199254740992) in table, json and yaml output alike. types.DecodeMutationOutput re-encodes the same value to inspect it, so mutation summaries inherited the rounded number too. types.DecodeJSON now decodes an any payload with json.Number and normalises integer literals that fit in int64 back to int64, and DecodeMutationOutput does the same for the plan/result fields it re-decodes. Non-integer literals and values outside int64 keep the float64 they had. Test: internal/studio/int64_precision_test.go runs a tool call against a stub Studio endpoint whose payload contains 2^53 + 1 and asserts the exact value in the decoded tree, in json, yaml and table rendering, and through types.DecodeMutationOutput. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/36962239183 With regards, GitHub Actions via GitBox
