-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
goal that is aborted needs to be cancelled before another NavigateToPose request is processed by controller_server #1795
Comments
@Jconn does this describe this issue? #1652 I think they're one in the same, but just want you to verify. Work is in progress to resolve, but its going to take a little bit of time because we have to update ROS2 design docs, rcl, and rclcpp to support. @naiveHobo is the one looking over this at the moment but I'm also open to more actively taking a role here as well to accelerate this getting in. |
Yeah at first glance that looks like the issue, sorry the for the double post. We are just starting to switch to foxy and master branch of nav, It would be good to get this fixed, before that happens I will have to stay on eloquent unless there is a workaround |
Does eloquent not show that issue? Maybe we can look at reverting something if that works. The process of getting the new updates will probably be at least another 4 weeks before its in master because we have to go through a bunch of stuff in rcl/rclcpp which are slower moving ships. Can you post a summary of your issue in that ticket as a follow up to make sure we have all of it in 1 place?
I like good news :-) |
Eloquent does show this issue! This is my mistake, there is something else going on in my robot that is causing more nav goals to abort with foxy than eloquent. I will post to the other ticket |
ah ok, thanks! |
Bug report
Required Info:
Ubuntu 18.04
fd2955a
Fast-RTPS
Steps to reproduce issue
Set a navigation goal through rviz, wait for the goal to fail due to
Failed to make progress
Set another navigation goal through rviz.
Expected behavior
Actual behavior
After the first goal is aborted, the second goal doesn't appear to be picked up by the controller server.
If I cancel the first goal (which I do through rviz), and then send the second goal again, everything works okay.
Additional information
Here is the log output from this behavior. The relevant part is after that first
Aborting Handle
I can only get the controller server to start spitting log info after I cancel the goal. TheReceived goal preemption request
are from me sendingNavigateToPose
requests through the rviz buttonThe text was updated successfully, but these errors were encountered: