Skip to content

[22658] Reliable volatile change dropped when all history acked (backport #5606) #5616

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

Merged
merged 2 commits into from
May 16, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 30, 2025

When the entire history is acked in volatile, given that the entries are deleted from the history, check_acked_status satisfies min_low_mark >= get_seq_num_min() because seq_num_min is unknown. This makes try_remove to fail, because it tries to remove changes but there were none. This causes prepare_change to not perform the changes, since the history was full and could not delete any changes.

@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 #5606 done by [Mergify](https://mergify.com).

@juanjo4936 juanjo4936 added this to the v2.10.7 milestone Jan 30, 2025
@MiguelCompany MiguelCompany self-requested a review May 14, 2025 09:35
@github-actions github-actions bot added the ci-pending PR which CI is running label May 14, 2025
juanjo4936 and others added 2 commits May 14, 2025 15:01
* Refs #22658: Regression test

Signed-off-by: Juanjo Garcia <[email protected]>

* Refs #22658: Fix bug

Signed-off-by: Juanjo Garcia <[email protected]>

* Refs #22658: corrected failing CI

Signed-off-by: Juanjo Garcia <[email protected]>

* Refs #22658: Included reviewer suggestions

Signed-off-by: Juanjo Garcia <[email protected]>

---------

Signed-off-by: Juanjo Garcia <[email protected]>
(cherry picked from commit 90790ce)
Signed-off-by: Eugenio Collado <[email protected]>
@MiguelCompany MiguelCompany force-pushed the mergify/bp/2.10.x/pr-5606 branch from 8871834 to c3d7a5c Compare May 14, 2025 13:02
@MiguelCompany MiguelCompany requested review from MiguelCompany and removed request for MiguelCompany May 14, 2025 13:02
@MiguelCompany MiguelCompany merged commit 753ee21 into 2.10.x May 16, 2025
13 of 18 checks passed
@MiguelCompany MiguelCompany deleted the mergify/bp/2.10.x/pr-5606 branch May 16, 2025 05:58
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.

3 participants