fix: enforce thread-safety during reranker initialization #815 - #819
Open
suhaniiz wants to merge 2 commits into
Open
fix: enforce thread-safety during reranker initialization #815#819suhaniiz wants to merge 2 commits into
suhaniiz wants to merge 2 commits into
Conversation
|
@suhaniiz is attempting to deploy a commit to the param20h's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
📋 PR Checklist
🔗 Related Issue
Closes #815
📝 What does this PR do?
This PR resolves concurrency and race condition vulnerabilities during model initialization in
app/reranker.py:_model_lockand_instance_lock) using Python's built-inthreading.Lock.get_reranker()singleton accessor and the internal lazy-loading_load_model()method.🗂️ Type of Change
🧪 How was this tested?
uvicorn app.main:app --reload)npm run devinsidefrontend/)📸 Screenshots (if UI change)
The double-check locking mechanic keeps performance optimal because threads only acquire the block lock during the very first initialization window. Once
_reranker_instanceand_modelare populated, subsequent access bypasses the lock entirely, ensuring zero overhead for concurrent production pipelines.✅ Self-Review Checklist
dev, notmainmainbranch or any HuggingFace deployment config