move_base action get's stuck if recovery behavior patience is exceeded
If a recovery behavior fails, calling the next immediatly breaks simple action client
If the last recovery behavior fails, we return that as move_base error instead of the error that triggered recovering
I was debugging the first, but realized the 2 other on the process
The solution for the first is to treat patience exceeded the same way as behavior failure. Then I realized the other 2 errors.
The solution for the 2nd is rather hackish, but a proper solution would require to implement the move_base action, for which I don't have time. In any case the previous code was incorrect.
move_baseaction get's stuck if recovery behavior patience is exceededI was debugging the first, but realized the 2 other on the process
The solution for the first is to treat patience exceeded the same way as behavior failure. Then I realized the other 2 errors. The solution for the 2nd is rather hackish, but a proper solution would require to implement the move_base action, for which I don't have time. In any case the previous code was incorrect.