René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Response leak in SSE handlers","articleBody":"I found a resource leak in the streamable HTTP client. When SSE streaming fails with an exception, the HTTP response isn't closed.\n\nLocation:\n`src/mcp/client/streamable_http.py`:\n- `_handle_sse_response` (line 336)\n- `_handle_resumption_request` (line 251)\n\nThe Issue:\npython\nasync def _handle_sse_response(self, response: httpx.Response, ...):\n    try:\n        event_source = EventSource(response)\n        async for sse in event_source.aiter_sse():\n            if is_complete:\n                await response.aclose()  # Only closed here\n                break\n    except Exception as e:\n        await ctx.read_stream_writer.send(e)\n        # response leaked!\n\nIf the SSE iteration raises an exception (malformed JSON, network error, etc.), the response is never closed.\n\nImpact:\nConnection pool gets exhausted in long-running clients, eventually causing new requests to hang or fail.\n\nFix:\ntry:\n    ...\nexcept Exception as e:\n    ...\nfinally:\n    await response.aclose()\n\nBoth methods need this fix.\n\nEnv:\nPython SDK version: 1.1.2 (or main branch)\nPython: 3.12\nTransport: StreamableHTTP","author":{"url":"https://github.com/certainly-param","@type":"Person","name":"certainly-param"},"datePublished":"2025-10-09T07:11:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/1450/python-sdk/issues/1450"}