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

Rapp manager does not shut down remaining caps #233

Open
bit-pirate opened this issue May 12, 2014 · 3 comments
Open

Rapp manager does not shut down remaining caps #233

bit-pirate opened this issue May 12, 2014 · 3 comments
Assignees
Labels
Milestone

Comments

@bit-pirate
Copy link
Collaborator

If stopping a cap has returned an error.

The rapp manager should store the error, attempt to shutdown the remaining caps and then report back the issue through there service response.

@bit-pirate
Copy link
Collaborator Author

This is also related to #165.

@bit-pirate
Copy link
Collaborator Author

Question @stonier and @jihoonl:
If stopping a rapp returns an error, should it be considered running or stopped?

If it should be considered stopped, I would make sure the capabilities are stopped in this case as well.

@bit-pirate
Copy link
Collaborator Author

If stopping a rapp returns an error, should it be considered running or stopped?

Conclusion of our talk is, that for now we consider the rapp stopped.

There is currently nothing implemented in the rapp manager, which could handle the situation, where stopping a rapp returns an error.

If specific use cases turn up, where this is a problem, we will add better handling specific for those use cases. At this moment it is hard to find those cases and hence even hard to add proper error/exception handling for them.

@stonier stonier added this to the Todo milestone Aug 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants