restore STOP_PROPAGATION handling for backward compatibility - #166
Merged
b3by merged 2 commits intoApr 21, 2026
Merged
Conversation
GaijinKa
changed the title
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.
Description
This PR restores handling of the
STOP_PROPAGATIONmessage in node.py for backward compatibilityPR type
Select all the labels that apply to this PR.
Key modifications and changes
_controlthread.Affected components
juturna/components/_node.pyAdditional context
The
STOP PROPAGATIONmessage may still cause issues in pipelines with fork and join paths. It’s not recommended to rely on it. If migrating to a different pattern isn’t possible, use it with caution