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

[22285] Fix comparison in is_update_allowed (backport #5414) #5416

Merged
merged 1 commit into from
Dec 31, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 25, 2024

Description

This fixes a bug in the comparison of the security attributes inside is_update_allowed of ReaderProxyData and WriterProxyData.

@Mergifyio backport 3.1.x 3.0.x 2.14.x 2.10.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.
  • 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.

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

@mergify mergify bot mentioned this pull request Nov 25, 2024
12 tasks
@MiguelCompany MiguelCompany added this to the v2.14.5 milestone Nov 25, 2024
@MiguelCompany MiguelCompany self-requested a review December 11, 2024 12:42
@github-actions github-actions bot added the ci-pending PR which CI is running label Dec 11, 2024
@EugenioCollado EugenioCollado self-requested a review December 26, 2024 14:00
Copy link
Contributor

@EugenioCollado EugenioCollado 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

@EugenioCollado
Copy link
Contributor

@Mergifyio rebase

* Refs #19927. Add unit test.

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

* Refs #19927. Fix issue in ReaderProxyData.

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

* Refs #19927. Fix issue in WriterProxyData.

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

---------

Signed-off-by: Miguel Company <miguelcompany@eprosima.com>
(cherry picked from commit 6b74b0d)
Copy link
Contributor Author

mergify bot commented Dec 30, 2024

rebase

✅ Branch has been successfully rebased

@EugenioCollado EugenioCollado force-pushed the mergify/bp/2.14.x/pr-5414 branch from 59f9fdc to 60fcd9f Compare December 30, 2024 10:13
@EugenioCollado EugenioCollado added ci-pending PR which CI is running and removed ci-pending PR which CI is running labels Dec 30, 2024
@EugenioCollado EugenioCollado merged commit c8bcb69 into 2.14.x Dec 31, 2024
18 checks passed
@EugenioCollado EugenioCollado deleted the mergify/bp/2.14.x/pr-5414 branch December 31, 2024 09:49
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.

2 participants