Expose discovered rosidle buffer backends through graph cache - #889
Draft
nvcyc wants to merge 1 commit into
Draft
Conversation
Signed-off-by: CY Chen <cyc@nvidia.com>
|
Tick the box to add this pull request to the merge queue (same as
|
nvcyc
marked this pull request as draft
July 30, 2026 08:16
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
3 participants
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
Pass discovered rosidl buffer backend metadata from Fast DDS user data into the shared graph cache.
Fast DDS already advertises and parses buffer backend metadata through endpoint user data. This change preserves that parsed metadata in graph endpoint info so tools such as
ros2 topic info -vcan display backend support for publishers and subscriptions.Is this user-facing behavior change?
Yes. Users can inspect Fast DDS topic endpoints and see advertised rosidl buffer backend support through ROS graph introspection tools.
Did you use Generative AI?
Yes. GPT-5.5 in Cursor was used to help draft changes in this pull request.
Additional Information
Depending on: