Repository navigation
fix: review ASGI protocol bridge (run_coroutine_threadsafe) under load #17
Description
Activity
Reopened after backlog review (2026-04-26): implementation is partial or the topic remains active (see
.github/ISSUE_BACKLOG/bodies/017.mdandPRIORITIES.md).Note: body file is
.github/ISSUE_BACKLOG/bodies/17.md(not 017).- added a commit that references this issue
on Apr 26, 2026 - linked a pull request that will close this issuefix(asgi): run handle_rsgi in executor to avoid run_coroutine_threads… #56
on Apr 26, 2026 - linked a pull request that will close this issuefix: harden ASGI bridge response scheduling under load #68
on Apr 27, 2026 - linked a pull request that will close this issuerelease: v0.2.0 hardening from dev #69
on Apr 27, 2026
Context
asyncio.run_coroutine_threadsafeand blockingfut.result()from syncresponse_*when native code calls into Python from a Tokio worker. Risk of deadlock under mixed load is documented; needs hardening.Work
httpxrequests. If deadlock appears, use a one-shotasyncio.Queuein the ASGI task to receive response actions without cross-threadresult(), or ananyio/triobridge.Acceptance criteria
uvicornsubprocess smoke test.