-
Notifications
You must be signed in to change notification settings - Fork 155
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
Run goalcallback asynchronously #496
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## ros2 #496 +/- ##
==========================================
- Coverage 42.82% 42.41% -0.40%
==========================================
Files 82 83 +1
Lines 7967 8043 +76
==========================================
Hits 3411 3411
- Misses 4556 4632 +76 ☔ View full report in Codecov by Sentry. |
A little hard to read, but it's right on the edge of "these lambdas should call a member function" and "it's short enough to all be inline". I'm OK with this. |
- Rename goalCallback() -> execCallback() - Run execCallback asynchronously and use future to know status of execution
* Run goalCallback in a seperate asynchronously * Clang-tidy fixes * Replace std::bind with lambdas * Add comment * Format --------- Co-authored-by: JafarAbdi <[email protected]>
- Rename goalCallback() -> execCallback() - Revert transition to lambdas, which made the code less readable
Finally address this comment in #461.
Disclaimer: I am not the original author of these changes.
This changes the behavior of the execute_task_solution_capability to not accept new execution requests if another request is currently processed. I assume the reason for this is to avoid interruptions because of incorrect execution commands. It is still possible to abort the execution with the CancelCallback.