Frun1na opened a new issue, #5272: URL: https://github.com/apache/rocketmq-dashboard/issues/5272
The rmqctl MCP client multiplexes requests and server-initiated messages on one stdio channel, so a decode failure is reported without saying which kind of frame it occurred in: a response frame and a server-initiated notification both surface as the same generic "invalid MCP message" error. When the server sends a slightly malformed response frame, the operator sees a decode failure that looks like it came from an unrelated push message, and it is impossible to tell whether the pending request should be retried. The decode error should name the frame kind it was parsing (response frame vs. server-initiated message), so the failure can be attributed to the right side of the channel. -- 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]
