| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
So to clarify, currently this is blocking from using the streamable-http transport inside clients such as Windsurf or Claude Desktop correct? |
Sorry, something went wrong.
|
Hmm, this shouldn't be blocking any clients, it is just adding error handling for a previously unhandled exception. Have you observed issues with this PR in certain clients? |
Sorry, something went wrong.
|
@bruno-oliveira This shouldn't be blocking anyone, but it does fix a huge security issue with remote servers. Currently anyone can lock up a server just by sending a bad payload #820 |
Sorry, something went wrong.
| await self._handle_incoming(responder) | ||
| if not responder._completed: # type: ignore[reportPrivateUsage] | ||
| await self._handle_incoming(responder) | ||
| except Exception as e: |
There was a problem hiding this comment.
I think is better to handle a specific exceptions before the general one, such as RuntimeError (Which mentioned in this issue)
Sorry, something went wrong.
There was a problem hiding this comment.
Given that the risk is the server becoming unresponsive, I believe catching all exceptions to isolate errors to a single request is correct.
Sorry, something went wrong.
There was a problem hiding this comment.
I don't think this is a valid answer from the package's point of view.
It makes it considerably hard to maintain the package if everything is except Exception.
Sorry, something went wrong.
|
I'm a bit baffled that a security issue like this is still open |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
| session_message = SessionMessage( | ||
| message=JSONRPCMessage(error_response)) |
There was a problem hiding this comment.
How this got merged?
Sorry, something went wrong.
…l#1227) The fix addresses stale session entries in _read_stream_writers after disconnect (202 + ClosedResourceError symptom from modelcontextprotocol#1227), not the EventSource auto-reconnect scenario from modelcontextprotocol#423 which is a client-side concern already mitigated by modelcontextprotocol#822 and modelcontextprotocol#1478.
| Back | FazBrowse Home | New Git URL |
Motivation and Context
This fixes an uncaught exception in the MCP server
How Has This Been Tested?
Via unit tests and locally.
Breaking Changes
None.
Types of changes
Checklist
Additional context