René's URL Explorer Experiment

Title: fix: chain exceptions in get_prompt and read_resource handlers by blackwell-systems · Pull Request #2542 · modelcontextprotocol/python-sdk · GitHub

Open Graph Title: fix: chain exceptions in get_prompt and read_resource handlers by blackwell-systems · Pull Request #2542 · modelcontextprotocol/python-sdk

X Title: fix: chain exceptions in get_prompt and read_resource handlers by blackwell-systems · Pull Request #2542 · modelcontextprotocol/python-sdk

Description: Summary Two raise statements in server/mcpserver/server.py discard the causal exception chain: Line 1112: raise ValueError(str(e)) → raise ValueError(str(e)) from e Line 451: raise ResourceError(...) → raise ResourceError(...) from exc Motivation and Context The same file uses from exc correctly at line 459. These two sites are inconsistent and lose the original traceback, making it impossible for callers to programmatically inspect the root cause via __cause__. Without from, Python shows "During handling of the above exception, another exception occurred" which is confusing. With from, it shows "The above exception was the direct cause of the following exception" and preserves the chain for isinstance() checks on __cause__. How Has This Been Tested? The change is purely additive (adds from clause) and does not alter control flow or exception types. Existing tests pass unchanged. Fixes #2541

Open Graph Description: Summary Two raise statements in server/mcpserver/server.py discard the causal exception chain: Line 1112: raise ValueError(str(e)) → raise ValueError(str(e)) from e Line 451: raise ResourceError(....

X Description: Summary Two raise statements in server/mcpserver/server.py discard the causal exception chain: Line 1112: raise ValueError(str(e)) → raise ValueError(str(e)) from e Line 451: raise ResourceError(....

Opengraph URL: https://github.com/modelcontextprotocol/python-sdk/pull/2542

X: @github

direct link

Domain: github.com

Links:

Viewport: width=device-width