SEP-2164: Standardize resource not found error code (-32602)#2164
Open
SEP-2164: Standardize resource not found error code (-32602)#2164
Conversation
pja-ant
force-pushed
the
sep/resource-not-found-error
branch
from
5faa2ee to
348d8e7
Compare
pja-ant
force-pushed
the
sep/resource-not-found-error
branch
from
348d8e7 to
310784e
Compare
pja-ant
changed the title
Contributor
|
related: modelcontextprotocol/python-sdk#1821 |
Member
|
Previous discussion (for reference): #1545. |
Contributor
Author
yeah I remember this, but didn't realize it was already so inconsistent. Any client has to handle various values anyway to work with real servers out there, so we might as well just trying and get all servers to converge. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This SEP standardizes the error code for resource not found from
-32002to-32602(Invalid Params), aligning with the JSON-RPC specification. Includes the draft spec change.