fix: main thread is blocked when canceling an execution #359
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.
Issue
Before, the join was called in the main thread. So when cancel is running, it will block other callbacks like odom callback from running. When cancel is running, the controller relies on odom callback to check if the robot is stopped and then it returns cancel. But as odom is not updated, the cancel keeps running.
After this change, it moves the block that runs cancel and updates the slot in a function and this function is called in a separate thread. So it does not block the main thread. I tested this by sending a goal with a different controller when cancel from one controller is running, and it seems to work. The next goal is executed after the first one is cancelled and the callbacks keep running in parallel.