Enhance exception handling in MCP server initialization and cleanup #2268
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.
Fixes an issue where MCP server connection failures (e.g., 401 Unauthorized) surfaced as confusing
BaseExceptionGroupexceptions instead of clear errors.What changed:
_unwrap_exception_group()to extract meaningful exceptions from anyio task group exception groupsconnect()to unwrap exceptions and re-raise the underlying error (e.g.,HTTPStatusErrorfor 401s)cleanup()to handle exception groups during cleanup and surface meaningful errorsResult:
Cryptic
BaseExceptionGroupwith multiple nested exceptions now become clearhttpx.HTTPStatusError: Client error '401 Unauthorized'messagesLogs before:
Logs After:
Repro Scripts:
main.py
server.py