Conversation
|
if we dont want to address "make topic_monitor launchfiles runnable with launch" this is ready for review |
wjwwood
left a comment
There was a problem hiding this comment.
lgtm, but I don't know how to answer the question about topic_monitor needing to be launch-able by launch.
|
sorry, didn't see the 'question' because updating the description doesn't send notifications (nor does editing in an @-mention). This looks good as is and I'll have a look at the topic monitor launching |
|
sounds good, thank you both for the the input |
|
waiting for ros2/ros2cli#23 to be resolved to update this before merging |
8e42c34 to
57a13a9
Compare
|
ok I think this is ready for another review (sorry I rebased so it's not easy to see identify new commits since the last review). I'll wait for ros2/ros2cli#23 to be merged and then merge this along updating all the tutorials accordingly @dhood I updated the topic_monitor README to match the current state, I'll leave it to you to update anything necessary if you decide to iterate on the launchfiles 😉 |
|
This might need to be updated when ament/ament_python#2 is merged to use the same approach as in the referenced PRs. |
|
thanks @dhood for the review and fixes! |
|
This previous comment still needs to be addressed. Otherwise the moved executables aren't runnable with |
|
Yeah I fell asleep before opening a PR. I'll do that this morning |
launch(fixes dummy_robot_bringup launch file fails when started withlaunch#140 )Not in this PR:
Depends on ros2/robot_state_publisher#8
Depends on ros2/ros2cli#23