[BUG] sync_node_executions fails for workflows with BranchNode #3274
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.
Tracking issue
Part of flyteorg/flyte#6490
Why are the changes needed?
When using flytekit's
FlyteRemote
and callingremote.wait
on an execution of a workflow that contains aBranchNode
, we will get following error:What changes were proposed in this pull request?
In some cases, the
execution.metadata.is_parent_node
for branch node is not True, which lead to the block without managing branch node separately. Moving the logic handling branch node before checkingis_parent_node
to handle both is and is not branch node casesHow was this patch tested?
integration test
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link
Summary by Bito
This pull request enhances the handling of branch nodes in Flytekit's execution logic, fixing a bug related to their management and ensuring they are handled correctly regardless of their parent node status. It introduces a new conditional workflow and tests to improve the library's robustness for complex workflows by preventing errors associated with missing attributes in branch nodes.