pilichoumao opened a new issue, #6322: URL: https://github.com/apache/rocketmq-dashboard/issues/6322
### Before Creating the Bug Report - [x] Searched issues and PRs. #4944 addresses confirmation cancellation, #6310 config output, and #6317 MCP stdio stdout; none handle failed interactive confirmation prompt writes. - [x] Defect in Studio rmqctl. - [x] Reproduced on current rocketmq-studio. ### Studio Version rocketmq-studio 5e4c39b053c35a5598cc79ff331b8a54e649d7b1, built from source. ### Runtime Environment macOS / Go CLI, App.Execute against an in-process HTTP endpoint. The test uses the existing character-device reader fixture to enter the actual defaultConfirm path. ### Connected RocketMQ Cluster No cluster/database required. The endpoint records dry-run/apply requests; no real offset is reset. ### Describe the Bug The interactive L2/L3 confirmation writes its warning and destination prompt to stderr with two fmt.Fprintf calls, ignoring their errors. A failed prompt can still consume an already available yes answer, run the preview and mutation, and exit successfully. ### Steps to Reproduce Run group reset-offset without --yes/--dry-run, with a fixed timestamp, terminal-like stdin containing yes and a failing stderr writer. Record outgoing HTTP requests. ### What Did You Expect to See? A failed prompt aborts before reading an answer or sending any HTTP request; the CLI exits nonzero and preserves the underlying output error. ### What Did You See Instead? Exit 0, two failed prompt writes, and two HTTP requests (preview followed by apply). ### Additional Context Scope is the two defaultConfirm prompt writes. Keep valid confirmations, Ctrl-C, --yes and explicit dry-runs intact; do not change the terminal gate, token protocol or other output paths. ### 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]
