-
Notifications
You must be signed in to change notification settings - Fork 252
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
Query offered QoS profiles for a topic and store in metadata #333
Conversation
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
4338e39
to
e57a6b8
Compare
Signed-off-by: Emerson Knapp <[email protected]>
Signed-off-by: Emerson Knapp <[email protected]>
e57a6b8
to
c2df921
Compare
Signed-off-by: Emerson Knapp <[email protected]>
@Karsten1987 ping for monday review :) I put more detail on the description for this one. |
@emersonknapp - please run this CI job |
The warnings in OSX are from rclcpp, unrelated to this change. |
Part of #125
Moves https://github.com/ros-tooling/aws-roadmap/issues/215 to Done
This change queries the currently offered QoS profiles for a given topic at the time of subscription, and stores them in the TopicMetadata. This does not use the queried QoS profile in any way, just stores it.
With this in, you will see the string-serialized profiles in both the metadata.yaml file and the sqlite topics table.
This does not handle new publishers that join after subscribing to a topic. We do not currently have a mechanism to change TopicMetadata after initial creation, and do not plan to add this ability for Foxy.
Once we have used the queried QoS profile to subscribe (upcoming change), we will need to make sure to notice late-joining publishers that offer a different QoS profile than we used to subscribe, to warn the user that this has happened.