Skip to content

Fix Reactive Sequence async control node validation - #1183

Merged
facontidavide merged 4 commits into
BehaviorTree:masterfrom
vivoeiva:fix/reactive-sequence-async-control
Oct 24, 2026
Merged

facontidavide merged 4 commits into
BehaviorTree:masterfrom
vivoeiva:fix/reactive-sequence-async-control

Conversation

@vivoeiva

@vivoeiva vivoeiva commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Also verify XML against AsyncFallback (not just AsyncSequence) under ReactiveSequence. Remove unreacheable cases with action nodes. Tests added for these cases, including one disabled (failing) test that needs further rework to catch async action nodes under ReactiveSequence.

facontidavide and others added 2 commits October 24, 2026 15:55
Async ACTION children are not detected by this check (the manifest does
not record whether an action is asynchronous); that is tracked by BehaviorTree#1184,
which should carry its own test, rather than a disabled one here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@facontidavide

Copy link
Copy Markdown
Collaborator

Thanks @vivoeiva, good catch: two AsyncFallback (or an AsyncSequence plus an AsyncFallback) under a ReactiveSequence livelock exactly like two AsyncSequence do, and only the latter was rejected. Dropping the three action names is also right, since nothing is registered under them as a CONTROL node. To move this forward I pushed a merge of master plus one commit that removes DISABLED_TwoAsyncActionsInReactiveSequence. Async actions aren't detected by this check, so that test belongs with #1184 rather than sitting here disabled. I'll squash-merge once CI is green.

@facontidavide
facontidavide merged commit 35d29c4 into BehaviorTree:master Oct 24, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants