-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RuntimeError: CurrentThreadExecutor already quit or is broken #491
Comments
Yup, this is why it's so hard to release changes to that code - I had been holding off releasing it until we could test it, and well, there you go. I don't have any immediate good ideas on how to solve this except by rolling back the original commit, but I'd rather not, so hopefully there's something more nuanced that's broken here. |
This is possibly related, although introduced earlier: |
andersk
added a commit
to andersk/asgiref
that referenced
this issue
Feb 5, 2025
Signed-off-by: Anders Kaseorg <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This code ping-pongs between
async_to_sync
→sync_to_async
→async_to_sync
→loop.call_later
→create_task
→sync_to_async
(although this sounds like a bizarre thing to do, it was minimized from a real problem in the Zulip server). It works with asgiref 3.7.2 and 3.8.1, but breaks with currentmain
(abc69a0) withRuntimeError: CurrentThreadExecutor already quit or is broken
. A Git bisection implicates 85d2445 as the first broken commit:The text was updated successfully, but these errors were encountered: