-
Notifications
You must be signed in to change notification settings - Fork 145
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
Support required nodes #179
Merged
Merged
+139
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kyrofa
commented
Feb 7, 2019
kyrofa
force-pushed
the
feature/174/required_nodes
branch
2 times, most recently
from
February 7, 2019 21:58
3e34dbf
to
039644e
Compare
Currently, the only way to specify that a given node is required for a given `LaunchDescription` is to register an `OnProcessExit` handler for the exit event of the required node that then emits a `Shutdown` event. Instead of requiring this boilerplate for a common use-case, add an `on_exit` parameter to `ExecuteProcess` that can take actions, and add a new action called `Shutdown` that immediately causes the launched system to shut down. This allows for the concept of a required node to be expressed simply with: launch_ros.actions.Node( # ... on_exit=Shutdown() ) Resolve ros2#174 Signed-off-by: Kyle Fazzari <kyle@canonical.com>
kyrofa
force-pushed
the
feature/174/required_nodes
branch
from
February 7, 2019 22:01
039644e
to
6fdc5c9
Compare
Closed
Signed-off-by: Kyle Fazzari <kyle@canonical.com>
wjwwood
approved these changes
Feb 7, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than a style nitpick, lgtm.
Signed-off-by: Kyle Fazzari <kyle@canonical.com>
wjwwood
approved these changes
Feb 7, 2019
wjwwood
reviewed
Feb 7, 2019
Signed-off-by: Kyle Fazzari <kyle@canonical.com>
wjwwood
approved these changes
Feb 7, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the only way to specify that a given node is required for a given
LaunchDescription
is to register anOnProcessExit
handler for the exit event of the required node that then emits aShutdown
event. Instead of requiring this boilerplate for a common use-case, This PR resolves #174 by adding anon_exit
parameter toExecuteProcess
that can take actions, and adding a new action calledShutdown
that immediately causes the launched system to shut down. This allows for the concept of a required node to be expressed simply with: