Retrieve HistoryQoS in discovery when available (jazzy backport #829)#846
Retrieve HistoryQoS in discovery when available (jazzy backport #829)#846mergify[bot] wants to merge 2 commits intojazzyfrom
HistoryQoS in discovery when available (jazzy backport #829)#846Conversation
Signed-off-by: Mario Dominguez <mariodominguez@eprosima.com> (cherry picked from commit e78f3f4) # Conflicts: # rmw_fastrtps_shared_cpp/include/rmw_fastrtps_shared_cpp/qos.hpp
|
Cherry-pick of e78f3f4 has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
Signed-off-by: Emerson Knapp <537409+emersonknapp@users.noreply.github.com>
HistoryQoS in discovery when available (backport #829)HistoryQoS in discovery when available (jazzy backport #829)
|
Pulls: #846 |
|
Ah, the history is lost now on the CI run, I don't know how it went. Perhaps after the Lyrical cut (so much contention on CI) we can re-run these backports. |
Description
This PR adds the HistoryQoS to the entities discovery callback when available.
Related tests PRs
HistoryQoSin test_info_by_topic rcl#1242HistoryQoSin test_ros2cli_daemon ros2cli#1040Fixes #684
Is this user-facing behavior change?
No
Did you use Generative AI?
No
Additional Information
Should be backported only to
KiltedThis is an automatic backport of pull request #829 done by Mergify.