fix: resolve edge handlers on successor ready, not on predecessor done - #438
Merged
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Change-Id: I0b0a785fda789c2c8812d20b79408ea0082c03a8
shentongmartin
force-pushed
the
fix/data_only_mapping
branch
from
September 2, 2025 09:31
5860ef9 to
26a2ebd
Compare
📊 Coverage Report: |
meguminnnnnnnnn
approved these changes
Sep 2, 2025
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
2 participants
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.
What type of PR is this?
fix an issue when a workflow node A 'indirectly maps' to another node B across branch, the field mapping on edge is eagerly resolved as soon as node A returns, which bypasses the branch control and may cause unexpected behavior.