-
Notifications
You must be signed in to change notification settings - Fork 79
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
Add support for launching nodes not in a package #82
Conversation
By making the package argument in launch_ros.actions.Node action optional. Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
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!
I left a couple of minimal comments.
(I thought a time ago about doing the same thing).
Going in! Thanks for the reviews! |
Is it possible this broken something? It's the only thing that's changed since yesterday when two new failures showed up on nightly/today's CI:
|
@@ -235,7 +239,9 @@ def parse(cls, entity: Entity, parser: Parser): | |||
node_name = entity.get_attr('node-name', optional=True) | |||
if node_name is not None: | |||
kwargs['node_name'] = node_name | |||
kwargs['package'] = parser.parse_substitution(entity.get_attr('pkg')) | |||
package = parser.parse_substitution(entity.get_attr('pkg'), optional=True) |
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.
This is the line where nightly/CI is failing.
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.
Yes, that's wrong. I'll fix it and check why it didn't fail before.
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.
Cool thanks, I've got it as part of this issue, so if you fix it could you comment there too? ros2/build_farmer#244
Precisely what the title says. Requiring nodes to be installed for
launch_ros.actions.Node
to be able to launch them is an unnecessary restriction. This way, packages with launch tests can have fixture node executables that do not get installed anywhere.Follow-up PR after #80. Useful in upcoming PRs.