We don't publish
your competitive advantage.

IFUnclosed client sessions and connectors warnings when using OpensearchVectorStore without explicitly closing the OpenSearch client.

THENImplement proper cleanup for the OpenSearch client in OpensearchVectorClient. Use a try...finally block to ensure the client is closed after operations, or override the destructor to close the client. For async usage, explicitly call client._os_async_client.close() when the session ends.

IFClosedResourceError when a client disconnects (e.g., sends DELETE over streamable HTTP) while a long-running tool handler is still executing, because the write stream is closed before the handler's response or log messages are sent.

THENImplement graceful shutdown cancellation: on client disconnect, cancel in-flight tool handlers and suppress ClosedResourceError when sending responses or logs. Place try/except around all send operations in tool handlers and log message methods to catch ClosedResourceError and handle it silently.

IFUnclosed client session and connector errors when using OpensearchVectorClient without proper cleanup on destruction.

THENImplement a try...finally pattern to ensure the OpenSearch client is closed after use, and explicitly close the async client session. For synchronous contexts, close the client in a destructor or using a context manager. For async contexts, await client.close() to avoid resource leaks.

IFWhen using stdio_client as a context manager, the subprocess is never cleaned up, causing the context to hang indefinitely after exiting the inner session.

THENEnsure that the subprocess spawned by stdio_client is properly terminated when the context manager exits. This may involve adding cleanup logic in the __aexit__ method to wait for the subprocess to finish or forcefully terminate it, and avoid blocking on pending reads/writes.