We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
use ros2/examples to test ros2 launch. Create a launch file with the following content and launch it.
from launch import LaunchDescription from launch_ros.actions import Node def generate_launch_description(): return LaunchDescription([ Node( package='examples_rclcpp_minimal_subscriber', node_executable='subscriber_lambda', node_name='subscriber_demo', output='screen', ), Node( package='examples_rclcpp_minimal_publisher', node_executable='publisher_lambda', node_name='publisher_demo', output='screen', ), ])
The terminal will display node's INFO message immediately, like:
[subscriber_lambda-1] [INFO] [subscriber_demo]: I heard: 'Hello, world! 0'
The terminal does not display any information at the beginning:
After a while, the terminal displays all information at once.
just like the subscriber is blocking.
I run the command
ros2 topic echo /topic
I can echo "/topic" normally.
Is this a bug, or is it like this?
The text was updated successfully, but these errors were encountered:
Check #188 and ros2/rcutils#168. Closing as duplicate.
Sorry, something went wrong.
No branches or pull requests
Steps to reproduce issue
use ros2/examples to test ros2 launch. Create a launch file with the following content and launch it.
Expected behavior
The terminal will display node's INFO message immediately, like:
Actual behavior
The terminal does not display any information at the beginning:
After a while, the terminal displays all information at once.
just like the subscriber is blocking.
Additional information
I run the command
I can echo "/topic" normally.
Is this a bug, or is it like this?
The text was updated successfully, but these errors were encountered: