fix: use per-thread persistent event loop - #8
Merged
Conversation
…losed' asyncio.run() creates a new event loop and closes it after each call. Async I/O libraries (httpx/anyio) schedule transport cleanup via loop.call_soon() after the coroutine returns; if the loop is already closed this raises 'RuntimeError: Event loop is closed' for every task invocation after the first successful one. Replace asyncio.run() with a threading.local()-backed helper that keeps one event loop alive per worker thread for the lifetime of the experiment run. Phoenix's ThreadPoolExecutor workers each get their own loop, which stays open across all example calls on that thread. Add a regression test that calls the wrapped task twice on the same thread to verify the loop is not closed between invocations.
zurfjereluhmie
changed the title
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.
No description provided.