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
{{ message }}
Repository navigation
Allow halting nodes to take multiple ticks to halt #1117
Is your feature request related to a problem? Please describe.
Currently if an Action node is halted, it has only 1 tick to stop and clean up. For actions that take non zero time to cancel (ROS action for example), it means stalling the tree in order to halt the action gracefully.
Describe the solution you'd like
Allow halting nodes to continue to be ticked outside of the active execution tree so the execution doesn't need to be blocked. Design considerations:
What does this mean for writing to ports?
Describe alternatives you've considered
As far as I can see now, the only alternative would be to detach a thread, which I feel would be an antipattern to the asynchronous execution pattern, and opens up all sorts of other risks/issues.
Additional context
As this would be a fairly major change, this is a proposal for BT5
Without breaking abi (and maybe api) would be difficult, but I would suggest to include in BT.CPP 5 for that reason, then those sort of breaks should be allowed right?
Activity
facontidavide commentedon Feb 9, 2026
I have no idea how to do this
tony-p commentedon Feb 11, 2026
I can think of a few ways, however before working anything out, how do you see it conceptually? If i made a solution would it be accepted?
facontidavide commentedon Feb 11, 2026
Of course contribution that are API, ABI compatible and don't affect performance, are welcome
tony-p commentedon Feb 11, 2026
Without breaking abi (and maybe api) would be difficult, but I would suggest to include in BT.CPP 5 for that reason, then those sort of breaks should be allowed right?
facontidavide commentedon Feb 11, 2026
Indeed. Start working on that and we can discuss it