Add constructor for McpError to allow setting error
field
#116
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.
Motivation and Context
Fix an issue where exception handling code fails with
AttributeError: 'McpError' object has no attribute 'error'
.The current callers of
McpError
seem to assume that it has a constructor that accepts anerror_data
but currently these get passed to the parent as the error message args (e.g. as if it were a pydantic object). This correctly sets the error code argument and sets the message string for the parent class.How Has This Been Tested?
Tested manually running an
sse_client
connected to a service that returns errors for unsupported methods when called.Breaking Changes
Types of changes
Checklist
Additional context