Disable intra-process-comms for transient_local publisher #220
Conversation
Signed-off-by: Yadunund <[email protected]>
|
So I'm not certain of this, but I have the feeling that this should actually all work in |
|
Fair point @clalancette ... In my issue I haven't specified the distro I was using (from source, mostly Iron with some additional backports). Will give it a try (maybe this patch could instead be targeted directly on 'iron' branch)? |
| auto publisher_options = rclcpp::PublisherOptions(); | ||
| // Explicitly disable intra_process_comms for this publisher alone to allow | ||
| // for this node to run in a component container with intra_process_comms enabled. | ||
| publisher_options.use_intra_process_comm = rclcpp::IntraProcessSetting::Disable; |
There was a problem hiding this comment.
I'm surprised this is necessary. Does this mean subscribers in the same process don't receive messages from publishers if the publishers have transient_local durability? I would have expected them to still get the messages through the rmw API.
There was a problem hiding this comment.
In Iron and before an exception would be thrown by rclcpp. I wasn't aware that support for this was added in Jazzy/Rolling. So we can close this PR
|
I'm going to close this for now, as we don't need this on |
Fix #219