-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
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
Update documentation to correct default publishing mode #3778
Conversation
This pull request has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/rmw-fast-dds-publication-mode-sync-vs-async-and-how-to-change-it/17153/3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM, @audrow you changed the behaviour in ros2/rmw_fastrtps#571
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change would need to be forward ported to Iron & Rolling
@@ -43,7 +43,6 @@ Mixing synchronous and asynchronous publications in the same node | |||
|
|||
In this first example, a node with two publishers, one of them with synchronous publication mode and the other one with asynchronous publication mode, will be created. | |||
|
|||
``rmw_fastrtps`` uses asynchronous publication mode by default. | |||
When the publisher invokes the write operation, the data is copied into a queue, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the publisher invokes the write operation, the data is copied into a queue, | |
One the one hand, on the asynchronous publication mode, when the publisher invokes the write operation, the data is copied into a queue, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm with @EduPonz 's comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fixup. You are right that we switched to synchronous mode by default in Humble and since.
I can't make this suggestion inline due to GitHub limitations, but I think we should restructure this a little more. In particular, I think we should swap the order of the two paragraphs, so that the paragraph talking about synchronous mode comes first. I think that makes the most sense, since that is the default. The text will then need some light editing to have it make more sense, but I think that will flow better overall.
I agree with @clalancette. I have refactored the paragraph and changed a bit the phrasing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks fantastic, thank you.
@Mergifyio backport rolling iron |
✅ Backports have been created
|
* Update documentation to correct default publishing mode (cherry picked from commit 87b1737)
* Update documentation to correct default publishing mode (cherry picked from commit 87b1737)
* Update documentation to correct default publishing mode (cherry picked from commit 87b1737) Co-authored-by: Giuseppe Rizzi <[email protected]>
* Update documentation to correct default publishing mode (cherry picked from commit 87b1737) Co-authored-by: Giuseppe Rizzi <[email protected]>
I checked both the documentation and the source code. The documentation shall be updated to reference the default publishing mode.