-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix: In AsyncPipeline cancel inflight tasks if a PipelineRuntimeError is raised by another component
#11499
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
Merged
+259
−114
Merged
fix: In AsyncPipeline cancel inflight tasks if a PipelineRuntimeError is raised by another component
#11499
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
12 changes: 12 additions & 0 deletions
12
releasenotes/notes/cancel-in-flight-tasks-on-error-8b9623a305717328.yaml
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| --- | ||
| fixes: | ||
| - | | ||
| Fixed a task leak in ``AsyncPipeline`` when running components concurrently. Previously, if one component | ||
| raised an error while sibling components were still running, those in-flight tasks were neither awaited nor | ||
| cancelled and kept running in the background until the event loop was torn down. They are now cancelled and | ||
| drained before the original error is re-raised. The same cleanup now also applies when iteration of | ||
| ``run_async_generator`` is stopped early (e.g. the consumer breaks out of the loop and closes the generator) | ||
| or the run is cancelled: any tasks still in flight are cancelled instead of leaking. | ||
| Note that cancellation only interrupts components that run natively async. Sync components are offloaded to a | ||
| worker thread, which cannot be interrupted and runs to completion in the background; its outputs are discarded, | ||
| so pipeline state stays consistent, but the component's side effects still complete. |
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.