pilichoumao opened a new issue, #6318: URL: https://github.com/apache/rocketmq-dashboard/issues/6318
### Before Creating the Bug Report - [x] Searched issues/PRs. This is the remaining mutation-summary boundary after merged #5262 (closed issue #5261). yyqdbngt already identified and proposed fixing this boundary in #5340, which was closed by the stale bot without merging. This report credits that prior contribution and narrows the current reproduction. - [x] Defect in Studio rmqctl. - [x] Reproduced on current rocketmq-studio. ### Studio Version rocketmq-studio 5e4c39b053c35a5598cc79ff331b8a54e649d7b1, built from source. ### Runtime Environment macOS / Go, App.Execute against an in-process Studio HTTP endpoint; no database/browser. ### Connected RocketMQ Cluster No live cluster needed. GroupResetOffsetToolHandler's plan queues contain long offset/lag values. A dry-run fixture returns the same shape; no offset mutation is executed. ### Describe the Bug The REST client now preserves numbers, but DecodeMutationOutput marshals and decodes the payload again with json.Unmarshal into Plan/Result interface fields. Default table summaries silently round those numbers. Structured JSON/YAML output bypasses this step and remains exact. ### Steps to Reproduce Return a PLANNED group-reset-offset response containing plan.before.queues[0].offset=9007199254740993. Execute group reset-offset --dry-run with default table output against that endpoint, then compare --output json / yaml. ### What Did You Expect to See? All formats show the exact queue offset. MutationOutput's nested plan and result numbers survive decoding. ### What Did You See Instead? The default summary contains 9007199254740992; JSON/YAML retain 9007199254740993. ### Additional Context Follow-up scope is only DecodeMutationOutput's decode and regression tests, using the existing client's UseNumber approach. No generic numeric normalization helper, REST client change, broker mutation, new API or reimplementation of #5262. Related prior contribution: https://github.com/apache/rocketmq-dashboard/pull/5340 by @yyqdbngt. ### 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]
