-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix: suppress MCP connection errors and handle LLM double-serialization #2434
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
wintrover
wants to merge
4
commits into
MoonshotAI:main
Choose a base branch
from
wintrover:fix/llm-serialization-and-mcp-errors-clean
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+92
−3
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
622d2dd
fix(asyncio): suppress MCP connection errors in event loop handler
wintrover d08c161
fix(todo): handle LLM double-serialization of todos array
wintrover b318589
fix(file): handle LLM double-serialization of edit parameter
wintrover 0a62ac9
fix(toolset): coerce LLM double-serialized arguments before validation
wintrover File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Early return bypasses delegation to original asyncio exception handler, silently swallowing non-MCP exceptions
The
returnat line 128 exits_asyncio_handlerbefore the delegation block at lines 142-146 runs. This completely swallows exceptions matching the string patterns — no telemetry, no logging, and no call to the original/default exception handler.This breaks the function's documented contract (line 142: "Delegate so the original logging behavior (or custom handler) runs") and is inconsistent with how
_excepthookhandles filtered exceptions — in_excepthook(lines 85-87), ignored exceptions (KeyboardInterrupt, SystemExit) still get delegated to the original handler, and this is verified bytest_original_handler_called_for_ignored_exceptions.Furthermore, the pattern matching is applied to ALL asyncio exceptions regardless of origin, not just MCP. The patterns like
"connection closed","connection refused", and"eof"could match exceptions from non-MCP sources such as the LLM API (APIConnectionError), the telemetry transport, web tools, or the wire server — all of which use asyncio networking. These would be silently discarded with no logging or diagnostics.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.