Hanabi9248 opened a new issue, #5030: URL: https://github.com/apache/rocketmq-dashboard/issues/5030
### 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 rocketmq-studio, commit 4c697f07acde460e2344375cb1f82669f5b270fd. ### Runtime Environment Windows amd64, Go 1.27.1. Reproduced using the existing CLI unit test. ### Connected RocketMQ Cluster Not required: this reproduces in the stdio proxy with its existing test session. ### Build Toolchain _No response_ ### Describe the Bug When stdin reaches EOF and the final call completes, stdioProxy.run can exit while its session notification channel still contains a message. The request result and notification arrive through separate channels, so selecting the result first can leave the notification unread. ### Steps to Reproduce From rmqctl: ```sh go test ./cmd -run '^TestStdioProxyForwardsServerNotification$' -count=10000 ``` This produced 14 failures in one run on the commit above. The test sends a progress notification before returning its response. ### What Did You Expect to See? Notifications already received during a call should be forwarded before the proxy finishes draining stdin and in-flight calls. ### What Did You See Instead? Failed iterations output only the response: ```json {"jsonrpc":"2.0","id":1,"result":{}} ``` The failure is `stdout missing notification` at mcp_stdio_proxy_test.go:121. ### Additional Context The loop condition only checks inputDone and activeCalls; it does not drain pending notifications before returning. This is separate from SIGTERM handling (#4650) and support for server-initiated requests (#4638). I can prepare a focused fix with a deterministic EOF regression test. ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
