fix(download): replace asyncio lock with thread lock - #87
Merged
Merged
Conversation
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.
Description
Fixes a thread-safety issue in the download token registry caused by using
asyncio.Lockto protect synchronous shared state accessed from multiple threads and event loops.The definitive audit confirmed that the actual failure mode is blocking/deadlock under cross-thread contention, rather than the originally suspected lost updates.
The fix uses
threading.Lockfor_DownloadRegistry, matching the existing synchronization pattern used byHTTPClientfor shared synchronous state.A dedicated regression test was also added using
threading.Barrierto force contention between threads and detect the vulnerableasyncio.Lockbehavior.The public API and existing download service behavior remain unchanged.
Related Issue
Fixes #BUG-002
Type of Change
Checklist
Screenshots (if applicable)
Not applicable.