Repository navigation
fix: harden ASGI bridge response scheduling under load - #68
Merged
Merged
Conversation
Replace run_coroutine_threadsafe(...).result() with a thread-safe outgoing queue drained on the main ASGI loop to reduce deadlock risk under concurrent load.
Document the queue-based response bridge and align the deadlock explanation with the new non-blocking send scheduling model.
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.
Summary
run_coroutine_threadsafe(...).result()calls in ASGI protocol response helpers with a thread-safe outgoing queuehttp.response.*messages on the main event loop whilehandle_rsgiruns in an executor threadTest plan
make test(maintainer run)tests/test_asgi_stress.py::test_asgi_50_concurrent_getsCloses #17