Repository navigation
Conversation
The module-level MCP pool lock bound to the first event loop where connections contended. A later event loop could then fail with a bound-to-a-different-event-loop error. Use weakly held locks keyed by the running event loop. Active and waiting operations keep a strong local reference to their lock. Idle locks and their loops are not retained, and same-loop serialization stays unchanged.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
If your worker calls
asyncio.run()for each job and the model asks for two MCP tools in one step, a later job could send a tool error back to the model. We were sharing a connection lock that could get bound to the first loop. Each event loop now gets its own lock.