fix: preserve exception propagation through transport cleanup #2591
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When exceptions occur during client initialization (e.g.,
McpErrorfrom server middleware), they were being swallowed and converted to "generator didn't yield" errors. This specifically affected in-memory transport where the server lifespan (including Docket's background worker context managers) is nested inside the client's task group - the complex cleanup chain was suppressing exceptions.Root cause: anyio task groups suppress exceptions when
cancel_scope.cancel()is called during cleanup.Fix: Capture exceptions before task group cleanup and re-raise them after the task group exits cleanly:
Also preserves
McpErrortype in_connect()so callers can catch protocol-level errors:Relevant to fixing #2531