-
Notifications
You must be signed in to change notification settings - Fork 160
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
Remove unused cli option #174
Conversation
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.
LGTM once it's rebased
16fc599
to
f13be2b
Compare
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.
LGTM (one tiny nitpick only)
@@ -47,9 +43,13 @@ def main(self, *, args): # noqa: D102 | |||
node_names = [n.full_name for n in node_names] | |||
|
|||
if args.node_name: | |||
if args.node_name not in node_names: | |||
node_name = args.node_name | |||
if not node_name[0] == '/': |
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.
Nitpick: node_name[0] != '/'
* Support required nodes 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> * Inherit from EmitEvent Signed-off-by: Kyle Fazzari <kyle@canonical.com> * Properly align type Signed-off-by: Kyle Fazzari <kyle@canonical.com> * Expose reason Signed-off-by: Kyle Fazzari <kyle@canonical.com>
* Asynchronously wait for load node service response Fixes ros2#171 By asychronously waiting for the service response, we can monitor if launch is shutting down and abandon the request so we don't block the shutdown process. Signed-off-by: Jacob Perron <jacob@openrobotics.org> * Add back debug log It was accidentally removed. Signed-off-by: Jacob Perron <jacob@openrobotics.org>
fixes #170
has to be rebased when #167 is merged.
This PR basically removed the obsolete argument
--transitions
for theros2 lifecycle get
command. The transitions can be displayed by invokingros2 lifecycle list [-a] <node_name>