-
Notifications
You must be signed in to change notification settings - Fork 18
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
Capability start/stop error handling #165
Comments
You are correct. Good catch. I'll tackle it ASAP. Out of curiosity, did you actually run into this issue or did you just notice the missing logic? |
just noticed. You might want to fix it sometime next week. rapp manager is under development now... |
Reminder for myself: Possible solutions:
|
Decided to implement the latter. |
Still not merged, but code is still lying around in caps_start_stop_fix branch should we need to push this in at some point. |
In the start_app logic,
start_app logic immediately returns failure response when it gets exception while enabling required capabilities. But it does not stop capabilities that are already started before getting into exception.
https://github.com/robotics-in-concert/rocon_app_platform/blob/hydro-devel/rocon_app_manager/src/rocon_app_manager/rapp_manager.py#L471-L498
The text was updated successfully, but these errors were encountered: