You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was recently a backporting update of 3.8 where this line changed from
for (size_t i = index + 1; i < childrenCount(); i++)
to
for (size_t i = 0; i < index; i++)
making ReactiveSequence unable to halt children that were previously running after a child whose state has just switched from SUCCESS to RUNNING. Meanwhile the bug seems to have been fixed in 4.x, but the fix has not been backported to 3.8. Is it possible to backport the fix of this problem as well? Thank you
The text was updated successfully, but these errors were encountered:
I don't dare to make an overall backport merge PR, but #817 is a backport of the particular commit that fixes the problem (+ a small optional defaults-changing commit that keeps the backward compatibility to v3.8.5)
…#817)
* ReactiveSequence and ReactiveFallback will behave more similarly to 3.8
* Reactive Sequence/Fallback defaulting to allow multiple async nodes
---------
Co-authored-by: Davide Faconti <davide.faconti@gmail.com>
Co-authored-by: Matej Vargovcik <vargovcik@robotechvision.com>
There was recently a backporting update of 3.8 where this line changed from
to
making ReactiveSequence unable to halt children that were previously running after a child whose state has just switched from SUCCESS to RUNNING. Meanwhile the bug seems to have been fixed in 4.x, but the fix has not been backported to 3.8. Is it possible to backport the fix of this problem as well? Thank you
The text was updated successfully, but these errors were encountered: