-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Python: fix(workflow): discard pending state after failed supersteps #7880
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
Open
Patel Namraa (Namraa310806)
wants to merge
10
commits into
microsoft:main
Choose a base branch
from
Namraa310806:fix/7859-discard-pending-state
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
956f43f
fix(workflow): discard pending state after failed supersteps
Namraa310806 59a705a
Merge branch 'main' into fix/7859-discard-pending-state
Namraa310806 b5e6ca0
Merge branch 'main' into fix/7859-discard-pending-state
Namraa310806 da0154c
fix: discard pending state before yielding failure events
Namraa310806 2848ad2
Merge branch 'main' into fix/7859-discard-pending-state
Namraa310806 debc9ba
Merge branch 'main' into fix/7859-discard-pending-state
Namraa310806 8bfce51
fix: discard pending state from failed supersteps
Namraa310806 f6f7535
Merge branch 'main' into fix/7859-discard-pending-state
Namraa310806 018f570
Merge branch 'main' into fix/7859-discard-pending-state
Namraa310806 8dd250b
Merge branch 'main' into fix/7859-discard-pending-state
Namraa310806 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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens when one fan-out executor fails while a sibling is still running?
asyncio.gather()in_run_iteration()propagates the first exception without cancelling the remaining children, so thisdiscard()can run while sibling handlers are still alive; after the nextawaitoryield, a sibling can callset_state()and repopulate_pending, which the nextWorkflow.run()then commits. Could_run_iteration()cancel and await every sibling before returning the failure, then discard once the superstep is inactive?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Evan Mattson (@moonbox3) — that makes sense. I’ll investigate the fan-out task lifecycle and verify this with a deterministic concurrent-sibling regression test.
If
asyncio.gather()can propagate the first exception while a sibling remains active, I’ll update_run_iteration()so the relevant sibling tasks are cancelled and awaited before the failure reaches theState.discard()boundary, while preserving the existing exception and cancellation semantics.I’ll also verify that the regression test fails with the current implementation and passes with the fix.