Skip to content

[23432] Pass value of TransportPriorityQosPolicy to transport layer#5933

Merged
MiguelCompany merged 24 commits intomasterfrom
feature/23432
Jul 23, 2025
Merged

[23432] Pass value of TransportPriorityQosPolicy to transport layer#5933
MiguelCompany merged 24 commits intomasterfrom
feature/23432

Conversation

@MiguelCompany
Copy link
Copy Markdown
Member

@MiguelCompany MiguelCompany commented Jul 14, 2025

Description

Contributor Checklist

  • Commit messages follow the project guidelines.
  • The code follows the style guidelines of this project.
  • Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
  • Any new/modified methods have been properly documented using Doxygen.
  • Any new configuration API has an equivalent XML API (with the corresponding XSD extension)
  • NO: Changes are backport compatible: they do NOT break ABI nor change library core behavior.
  • Changes are API compatible.
  • New feature has been added to the versions.md file (if applicable).
  • New feature has been documented/Current behavior is correctly described in the documentation.
  • N/A: Applicable backports have been included in the description.

Reviewer Checklist

  • The PR has a milestone assigned.
  • The title and description correctly express the PR's purpose.
  • Check contributor checklist is correct.
  • If this is a critical bug fix, backports to the critical-only supported branches have been requested.
  • Check CI results: changes do not issue any warning.
  • Check CI results: failing tests are unrelated with the changes.

@MiguelCompany MiguelCompany added this to the v3.4.0 milestone Jul 14, 2025
@MiguelCompany MiguelCompany force-pushed the feature/23432 branch 3 times, most recently from 63f06ce to ebafca3 Compare July 14, 2025 10:19
@MiguelCompany MiguelCompany requested a review from Mario-DL July 14, 2025 10:20
@github-actions github-actions Bot added the ci-pending PR which CI is running label Jul 14, 2025
@MiguelCompany MiguelCompany added the needs-review PR that is ready to be reviewed label Jul 14, 2025
@MiguelCompany MiguelCompany requested review from richiprosima and removed request for richiprosima July 14, 2025 12:14
@MiguelCompany MiguelCompany requested review from richiprosima and removed request for richiprosima July 15, 2025 06:07
@MiguelCompany MiguelCompany requested review from Mario-DL and removed request for Mario-DL July 15, 2025 06:27
Copy link
Copy Markdown
Contributor

@Mario-DL Mario-DL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apart from the comments below, I was wondering whether we should include a logic in the transport_priority within TopicQoS i.e should we keep it updated to the same value as the one in the writer ? (I think that the standard does not mention nothing, nor any requirement in terms of compatibility rule)
What if the value is changed in runtime in the Topic QoS ? If we are just "ignoring" it I think we could document that.

Comment thread include/fastdds/dds/builtin/topic/TopicBuiltinTopicData.hpp
Comment thread src/cpp/rtps/transport/UDPTransportInterface.h Outdated
@Mario-DL Mario-DL added doc-pending Issue or PR which is pending to be documented versions-pending labels Jul 15, 2025
@MiguelCompany MiguelCompany requested a review from Mario-DL July 15, 2025 12:57
Mario-DL
Mario-DL previously approved these changes Jul 16, 2025
Copy link
Copy Markdown
Contributor

@Mario-DL Mario-DL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Mario-DL Mario-DL removed the needs-review PR that is ready to be reviewed label Jul 16, 2025
@MiguelCompany MiguelCompany removed the doc-pending Issue or PR which is pending to be documented label Jul 17, 2025
@MiguelCompany MiguelCompany requested a review from Mario-DL July 18, 2025 11:22
Mario-DL
Mario-DL previously approved these changes Jul 21, 2025
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
…nc`.

Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
…ransport.

Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
…erQos.

Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
Copy link
Copy Markdown
Contributor

@Mario-DL Mario-DL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with green CI

@Mario-DL Mario-DL added ready-to-merge Ready to be merged. CI and changes have been reviewed and approved. and removed ci-pending PR which CI is running labels Jul 23, 2025
@MiguelCompany MiguelCompany merged commit 95410fc into master Jul 23, 2025
36 of 38 checks passed
@MiguelCompany MiguelCompany deleted the feature/23432 branch July 23, 2025 05:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-to-merge Ready to be merged. CI and changes have been reviewed and approved.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants