Bonsai
unexpected effects of disabled but connected nodes? #2006
-
|
I created a frequently updated 
In this case mySubject is only initialized once but is propagated 3 times. When the commented out node is deleted or simply connected on the other end like the rest of the The same behavior happens also if I e.g. replace Workflow attached below. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
@glopesdev seems like a bug where the expression tree is seeing the disabled node as a hanging branch and adding a publish. Can you confirm? I am tentatively opening an issue with this. Thanks for reporting! |
Beta Was this translation helpful? Give feedback.
-
|
Yes, this is a known "quirk". There are is an intrinsic ambiguity in fully disabled branches between whether the source should be connected directly to the merge, or the branch removed entirely. A dangling branch is ultimately still merged back into the workflow output so it falls into this ambiguity too. It is awkward though so raising the issue is fine and we can at least track the discussion on the impact of different ways to resolve it. |
Beta Was this translation helpful? Give feedback.
Yes, this is a known "quirk". There are is an intrinsic ambiguity in fully disabled branches between whether the source should be connected directly to the merge, or the branch removed entirely. A dangling branch is ultimately still merged back into the workflow output so it falls into this ambiguity too.
It is awkward though so raising the issue is fine and we can at least track the discussion on the impact of different ways to resolve it.