ros2 topic pub creates two publishers
See original GitHub issueAs mentioned here the QOS event callback triggers a call to rmw_create_publisher
twice for the same topic on the same node.
Where this might be supported for DDS implementations, it might lead to UB for non-DDS RMWs, c.f. https://github.com/ros2/rmw_iceoryx/issues/28
Is there a way to create a create incompatible QoS with creating only one publisher?
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (17 by maintainers)
Top Results From Across the Web
Writing a simple publisher and subscriber (Python)
Goal: Create and run a publisher and subscriber node using Python ... You created two nodes to publish and subscribe to data over...
Read more >Exchange Data with ROS 2 Publishers and Subscribers
Create a publisher that sends ROS 2 string messages to the /chatter topic. chatterPub = ros2publisher(node_1,"/chatter","std_msgs/String");.
Read more >How to work with ros2 topics from the command line
String(data='Hello World!') publishing #2: std_msgs.msg. ... Basically, to publish to a topic, you do ros2 topic pub [topic_name] [message_type] ...
Read more >How to Publish & Subscribe to a ROS2 Topic [UPDATED]
ROS2 Tutorials # 2 : How to Publish & Subscribe to a ROS2 Topic [UPDATED].
Read more >3: Creating a ROS 2 Pub-Sub Subscription using TypeScript
Once node-publisher is running and publishing messages, you should see subscription messages begin dribbling to stdout as shown below. Using The ros2 topic...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Reverting #410 sounds good to me.
If the creation of the publisher failed, it should be automatically cleaned up, and the user shouldn’t need to do that manually. It’s worth investigating why it wasn’t cleaned up correctly and fixing it too.
@mm318 I can confirm that https://github.com/ros2/rclpy/pull/553 solves the problem.