Skip to content
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

[21165] Correctly initialize MatchingFailureMask constants to be used with the std::bitset API (backport #4922) #4925

Merged
merged 1 commit into from
Jun 11, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jun 10, 2024

Description

This PR changes the values of the MatchingFailureMask so they can be directly used through the std::bitset API. Before this PR, the following code:

EDP::MatchingFailureMask mask;
mask.set(EDP::MatchingFailureMask::different_typeinfo);

resulted in a C++ exception as follows:

"bitset::set: __position (which is 16) >= _Nb (which is 16)"

@Mergifyio backport 2.14.x 2.13.x 2.10.x 2.6.x

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

  • N/A: Any new/modified methods have been properly documented using Doxygen.

  • N/A: Any new configuration API has an equivalent XML API (with the corresponding XSD extension)

  • Changes are backport compatible: they do NOT break ABI nor change library core behavior.

  • Changes are API compatible.

  • N/A: New feature has been added to the versions.md file (if applicable).

  • N/A: New feature has been documented/Current behavior is correctly described in the documentation.

  • 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.
  • Check CI results: changes do not issue any warning.
  • Check CI results: failing tests are unrelated with the changes.

This is an automatic backport of pull request #4922 done by [Mergify](https://mergify.com).

@mergify mergify bot added the conflicts Backport PR wich git cherry pick failed label Jun 10, 2024
Copy link
Contributor Author

mergify bot commented Jun 10, 2024

Cherry-pick of 5e1f1dd has failed:

On branch mergify/bp/2.14.x/pr-4922
Your branch is up to date with 'origin/2.14.x'.

You are currently cherry-picking commit 5e1f1dd22.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   test/unittest/rtps/discovery/EdpTests.cpp

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   include/fastdds/rtps/builtin/discovery/endpoint/EDP.h

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

…the `std::bitset` API (#4922)

* Refs #21165: Add regression test

Signed-off-by: eduponz <eduardoponz@eprosima.com>

* Refs #21165: Init MatchingFailureMask constants as normal uints

Signed-off-by: eduponz <eduardoponz@eprosima.com>

* Refs #21165: Apply Ricardo's suggestions

Signed-off-by: eduponz <eduardoponz@eprosima.com>

---------

Signed-off-by: eduponz <eduardoponz@eprosima.com>
(cherry picked from commit 5e1f1dd)
@EduPonz EduPonz self-requested a review June 11, 2024 07:37
@EduPonz EduPonz removed the conflicts Backport PR wich git cherry pick failed label Jun 11, 2024
@EduPonz EduPonz self-requested a review June 11, 2024 07:37
@github-actions github-actions bot added the ci-pending PR which CI is running label Jun 11, 2024
@EduPonz EduPonz merged commit 6d10771 into 2.14.x Jun 11, 2024
13 of 17 checks passed
@EduPonz EduPonz deleted the mergify/bp/2.14.x/pr-4922 branch June 11, 2024 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-pending PR which CI is running
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant