Serialize encapsulation header on buffer aware topics (backport #891) - #893
Open
mergify[bot] wants to merge 1 commit into
Open
Serialize encapsulation header on buffer aware topics (backport #891)#893mergify[bot] wants to merge 1 commit into
mergify[bot] wants to merge 1 commit into
Conversation
* Serialize encapsulation when publishing Signed-off-by: Miguel Company <miguelcompany@eprosima.com> * Read encapsulation when taking Signed-off-by: Miguel Company <miguelcompany@eprosima.com> * Catch and log error when reading encapsulation header. Signed-off-by: Miguel Company <miguelcompany@eprosima.com> * Fix typo Signed-off-by: Miguel Company <miguelcompany@eprosima.com> * Fix linters Signed-off-by: Miguel Company <miguelcompany@eprosima.com> --------- Signed-off-by: Miguel Company <miguelcompany@eprosima.com> (cherry picked from commit 742f713)
Author
|
Tick the box to add this pull request to the merge queue (same as
|
|
Pulls: #893 |
fujitatomoya
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
While creating a native DDS consumer for rosidl buffer custom topics, I discovered that the encapsulation header required by the RTPS standard is not added for the reader-GUID-based topics.
This PR adds the encapsulation header when publishing, and consumes it when taking.
Is this user-facing behavior change?
No, but the custom serialization changes.
I would nonetheless consider backporting to lyrical.
Did you use Generative AI?
No.
Additional Information
I verified that the GPU buffer transport tutorial works with these changes
This is an automatic backport of pull request #891 done by Mergify.