You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "Frun1na (via GitHub)" <gi...@apache.org> on 2026/10/01 15:21:53 UTC

[I] [Bug] MCP decode error for a response frame does not name the frame kind [rocketmq-dashboard]

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: commits-unsubscribe@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug] MCP decode error for a response frame does not name the frame kind [rocketmq-dashboard]

Posted by "Frun1na (via GitHub)" <gi...@apache.org>.
Frun1na commented on issue #5272:
URL: https://github.com/apache/rocketmq-dashboard/issues/5272#issuecomment-5934525547

   Fix: #5273


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug] MCP decode error for a response frame does not name the frame kind [rocketmq-dashboard]

Posted by "Frun1na (via GitHub)" <gi...@apache.org>.
Frun1na commented on issue #5272:
URL: https://github.com/apache/rocketmq-dashboard/issues/5272#issuecomment-6044303572

   Friendly ping — the fix for this is in #5273 and is waiting for review; keeping the issue from the stale bot meanwhile.


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug] MCP decode error for a response frame does not name the frame kind [rocketmq-dashboard]

Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins commented on issue #5272:
URL: https://github.com/apache/rocketmq-dashboard/issues/5272#issuecomment-6078690740

   Resolved by #484d02fb7 (merged into `rocketmq-studio` as 5262); the fix was contributed in #5273, which we folded into that change.


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Bug] MCP decode error for a response frame does not name the frame kind [rocketmq-dashboard]

Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins closed issue #5272: [Bug] MCP decode error for a response frame does not name the frame kind
URL: https://github.com/apache/rocketmq-dashboard/issues/5272


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org