-
Notifications
You must be signed in to change notification settings - Fork 45
Can't run two goals in a row #71
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
Comments
I don't see any reason for that to be happening. Adding some prints in to see what's being sent might be helpful. I believe I see that the |
Just to add to this. It works fine if I send the exact same goal twice. But if I change the first and last point, it breaks. |
Print out the goal_msg and see what it says. If its right, then the issue is on the server side. If its wrong, then its something in the python. |
First goal: Second goal: |
I also tried setting |
Actually, this pull request seems to reference this issue #43 .
|
Edit: Ah OK - want to submit that as a PR for just those changes needed? |
Alright, I''ve made the pull request |
I would also like to backport to iron, how would I go about that? |
Cherry pick and open a PR against iron/humble :-) |
Alright, I made a PR to backport a few of my other PR's |
@Marc-Morcos can you do humble too while you're at it? |
I could, but I wont have a valid environment to test it, so I probably shouldn't right? |
No problem - I'll put it on my queue |
@SteveMacenski - Is there any way we can get this backported to the humble branch? I am seeing issues when I run multiple coverages in a row and this fixed the issue. Confirmed on my robot testing IRL Happy to help with testing or doing the PR if you'd prefer |
@shawnhanna feel free to open the PR, I should be able to merge it in < 1 hr |
Added. Thanks @SteveMacenski |
If I run the demo,
replacing the main function of demo_coverage.py with
I get the following error
[coverage_server]: Invalid GML File or Coordinates: Outer polygon malformed, first element must equal last!
The text was updated successfully, but these errors were encountered: