Skip to content
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

Terminal status for goals #83

Closed
MoffKalast opened this issue Feb 18, 2021 · 3 comments
Closed

Terminal status for goals #83

MoffKalast opened this issue Feb 18, 2021 · 3 comments
Assignees

Comments

@MoffKalast
Copy link
Contributor

MoffKalast commented Feb 18, 2021

It seems that occasionally when using move_basic through the action client it's possible to get the following result when preempting:

[ WARN] [1613663891.808006341, 985.273000000]: Your executeCallback did not set the goal to a terminal status.
This is a bug in your ActionServer implementation. Fix your code!
For now, the ActionServer will set this goal to aborted

Upon which move_basic seems to lock up sometimes. The solution would be to check in which case it's possible to end the callback without calling set_something for the goal before returning. Found in nav-features-aislemode branch, possibly a problem in others as well.

@MoffKalast
Copy link
Contributor Author

After more research it seems to be a bug in the action client itself, so we'll have to watch to never get into situations where this can occur instead.

ros/actionlib#126

@dorkamotorka
Copy link
Contributor

From my experience this is usually not a bug in the actionServer but rather our code that set a goal two time successful or aborting the same goal multiple times.

@MoffKalast
Copy link
Contributor Author

Well in this case it may just be both 😑

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants