Frun1na opened a new issue, #4945: URL: https://github.com/apache/rocketmq-dashboard/issues/4945
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version branch: `rocketmq-studio` git commit id: `1ef5d860` (upstream tip at the time of the report) deployed as: built from source ### Runtime Environment Verified by code tracing and unit tests on `rocketmq-studio` @ `1ef5d860` (vitest for `web/`, JUnit for `server/`), not against a specific browser or deployment. ### Connected RocketMQ Cluster Not cluster-specific: the defect lives in the code path and reproduces on any deployment where the trigger condition below holds. ### Describe the Bug 1. Ctrl-C while a request is in flight surfaces as `error [UNAVAILABLE]: context canceled` with a network troubleshooting hint, because the wrapped error matches the net.Error matcher. 2. At the L2/L3 `Type "yes" to continue:` prompt, Ctrl-C is silently ignored (the stdin read is not bound to the command context), and a `yes` typed afterwards proceeds with an already-canceled context, failing with the same UNAVAILABLE message. ### Steps to Reproduce 1. Run any slow command (e.g. `rmqctl topic list --instance-id X` against a stalled server) and press Ctrl-C mid-request: output is `error [UNAVAILABLE]: context canceled`. 2. Run an L3 tool interactively (e.g. `rmqctl consumer delete ...`), press Ctrl-C at the WARNING prompt, then type `yes`: the confirmation 'succeeds' and the command fails with `error [UNAVAILABLE]: context canceled`. ### What Did You Expect to See? Ctrl-C is reported as a cancellation (distinct code and hint), and the confirmation prompt aborts on the interrupt instead of accepting an answer after it. ### What Did You See Instead? The user is directed to debug a healthy server; a canceled confirmation can still send the mutation. -- 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]
