Skip to content

Fix: Replace threading.Lock with anyio.Lock for Ray deployment compatibility #1151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

only-weng
Copy link

Replace threading.Lock with anyio.Lock for Ray deployment compatibility

Motivation and Context

When deploying StreamableHTTP services with Ray, we encountered serialization issues because threading.Lock objects cannot be pickled/serialized. This causes deployment failures when Ray tries to serialize the session manager objects across worker processes.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

…ibility

- Replace threading.Lock() with anyio.Lock() in StreamableHTTPSessionManager
- This resolves serialization issues when deploying StreamableHTTP services with Ray
- threading.Lock objects cannot be pickled/serialized, causing deployment failures
- anyio.Lock provides equivalent functionality while being fully serializable
- Update lock usage from 'with' to 'async with' for proper async context
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant