[FIX] DockerCommandLineCodeExecutor multi event loop aware #6402
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.
Why are these changes needed?
Problem
Previously, in
DockerCommandLineCodeExecutor
, cancellation tasks were added directly toself._cancellation_tasks
usingasyncio.create_task()
:This caused issues when cancellation tasks were created from multiple event loops, leading to loop mismatch errors during executor shutdown.
Solution
This PR fixes the issue by introducing a dedicated internal event loop for managing cancellation tasks.
Cancellation tasks are now scheduled in a fixed event loop using
asyncio.run_coroutine_threadsafe()
:Additional Changes
Note
This change ensures that all cancellation tasks are handled consistently in a single loop, preventing cross-loop conflicts and improving executor stability in multi-threaded environments.
Related issue number
Closes #6395
Checks