Fix for #57 only works reliably for the very first goal

[robin-mueller]

As I commented after the fix for the original issue #57 , cancelGoal() still doesn't work correctly for pre-response action cancellation. The issue now is, that goal_handle_ is not reset after a previous goal has terminated, which causes this condition to always become true after the first goal response. Therefore the function misleadingly assumes for any subsequent goals that the corresponding response has already arrived. As a result, an rclcpp_action::UnkownGoalError is thrown in action_client->async_get_result() if cancelGoal() is called when the current goal has not arrived yet, since goal_handle_ refers to the previous, already terminated goal.

We either have to reset goal_handle_ appropriately, or refer to the currently relevant goal uuid if we want to verify that the response has arrived.

I also suggested an entirely different implementation of RosActionNode here, which would prevent this issue from ocurring in the first place (Behavior A: Wait for goal response during initial tick).

[robin-mueller]

Is there any update on this topic? If we decide on an approach to fix this issue, I can prepare a pull request.

[fafux]

I had the same problem when canceling goals multiple times (working only the very first time) getting as result rclcpp_action::UnkownGoalError. Adding goal_handle_ = nullptr; at this line fixes.

[flbeck]

I am currently experiencing a similar issue mentioned in #110 and the fix provided by @fafux seems to fix this too.