Revision history [back]

There is a race condition that fails when roslaunching, but there is an option --wait-for-start to avoid it

https://github.com/ros/ros_comm/issues/1942

<?xml version="1.0"?>
<launch>
  <node name="pub" pkg="rostopic" type="rostopic" args="pub /foo std_msgs/Float64 0.5 -r 1" />
  <node name="foobar" pkg="topic_tools" type="transform" args="/foo /bar std_msgs/Float64 'm' --wait-for-start"/>
</launch>

That option really ought to be true by default.

There is a race condition that fails when roslaunching, but there is an option --wait-for-start to avoid itit --wait_for_start

https://github.com/ros/ros_comm/issues/1942

(it's the same code in relay_field and transform)

<?xml version="1.0"?>
<launch>
  <node name="pub" pkg="rostopic" type="rostopic" args="pub /foo std_msgs/Float64 0.5 -r 1" />
  <node name="foobar" pkg="topic_tools" type="transform" args="/foo /bar std_msgs/Float64 'm' --wait-for-start"/>
</launch>

That option really ought to be true by default.

There is a race condition that fails when roslaunching, roslaunching with a fresh roscore, but there is an option to avoid it --wait_for_start

https://github.com/ros/ros_comm/issues/1942

(it's the same code in relay_field and transform)

<?xml version="1.0"?>
<launch>
  <node name="pub" pkg="rostopic" type="rostopic" args="pub /foo std_msgs/Float64 0.5 -r 1" />
  <node name="foobar" pkg="topic_tools" type="transform" args="/foo /bar std_msgs/Float64 'm' --wait-for-start"/>
</launch>

That option really ought to be true by default.