fix(concurrency): fix issue for data leakage across sessions - #14
Merged
Merged
Conversation
…r, and pool DB connections - Use threading.local for orchestrator retrieval state to prevent cross-request leakage - Add threading lock around LLM rate limiting to prevent race conditions - Implement psycopg2 ThreadedConnectionPool with robust SQLite fallback and connection timeouts
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
1 participant
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.
Use threading.local for orchestrator retrieval state to prevent cross-request leakage
Add threading lock around LLM rate limiting to prevent race conditions
Implement psycopg2 ThreadedConnectionPool with robust SQLite fallback and connection timeouts