Repository navigation
Fix event-loop lifetime in process-parallel workers - #556
Merged
codelion merged 1 commit intoOct 29, 2026
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.
Summary
Fix event-loop lifetime management in OpenEvolve's process-parallel workers.
Repeated
asyncio.run()calls can close event loops while cached asynchronous clients retain resources bound to those loops. Subsequent worker operations may then fail withRuntimeError: Event loop is closed.Changes
Validation
Tested against upstream commit
bcf63da435ed6e89b751bddaf01dbfc0744a5320.Earlier isolated investigations reproduced the event-loop lifecycle failure and supported the repair.
Scope and limitations
The change is limited to
openevolve/process_parallel.pyandtests/test_worker_loop_lifecycle.py.The full local unit suite passed, but compatibility with every provider and deployment configuration remains unverified. No performance improvement is claimed.
Feedback on the worker lifecycle and cleanup approach is welcome.