Add qos parameter for wait_for_message function (backport #2903)#2907
Merged
fujitatomoya merged 1 commit intohumblefrom Jul 17, 2025
Merged
Add qos parameter for wait_for_message function (backport #2903)#2907fujitatomoya merged 1 commit intohumblefrom
fujitatomoya merged 1 commit intohumblefrom
Conversation
Signed-off-by: Sriharsha Ghanta <ghanta1996@gmail.com> Signed-off-by: Alejandro Hernandez Cordero <ahcorde@gmail.com> Co-authored-by: Alejandro Hernandez Cordero <ahcorde@gmail.com> (cherry picked from commit 2fcef70)
fujitatomoya
approved these changes
Jul 16, 2025
Collaborator
|
Pulls: #2907
|
Collaborator
|
https://ci.ros2.org/job/ci_linux-rhel/3781/ are unrelated. |
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
2 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
A small change to include the QoS settings as one of the parameters for
rclcpp::wait_for_message. This is useful in cases where we want just to get the last published message on the topic, rather than always waiting for a new message.Fixes # (issue)
Is this user-facing behavior change?
Did you use Generative AI?
No
Additional Information
This is an automatic backport of pull request #2903 done by [Mergify](https://mergify.com).