python-sdk

Summary cancel the stdio client task group before closing its memory streams during shutdown move memory stream teardown until after the task group has exited add a regression test that exits while is blocked on a zero-buffer send Problem starts background tasks that read process stdout and forward messages into a zero-buffer memory stream. If the caller exits the context without consuming , can block on . Before this change, the cleanup path closed while was still running inside the task group. That raises and surfaces as an during context exit. Fix The cleanup sequence now cancels the task group before any of the memory streams it owns are closed. The stream handles are closed only after the task group has exited, so and are no longer racing against stream teardown. Validation reproduced the failure locally on current with a minimal stdio server that writes one JSON-RPC message and then idles

Summary guard the low-level exception logging path when the session write stream is already closed add regression coverage for both and from Problem When the server receives an exception from the stream during shutdown, tries to emit an internal error log notification through . If the session write stream has already been torn down, that best-effort log write can raise or and crash the enclosing task group. Fix Treat exception logging in this shutdown path as best-effort. If the write stream is already gone, skip the log notification and continue handling the original shutdown flow. Validation