Skip to content

[23654] Change non_blocking_send threshold to sendBufferSize (backport #6073)#6077

Merged
juanlofer-eprosima merged 1 commit into3.3.xfrom
mergify/bp/3.3.x/pr-6073
Oct 9, 2025
Merged

[23654] Change non_blocking_send threshold to sendBufferSize (backport #6073)#6077
juanlofer-eprosima merged 1 commit into3.3.xfrom
mergify/bp/3.3.x/pr-6073

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Oct 7, 2025

Description

Currently the non blocking size feature assumes that the size of TCP sockets allocated by the OS is twice the value requested (sendBufferSize). However, it has been observed that the actual reserved value may fall below that value, hence blocking when the buffer gets full and ruining the purpose of this feature.

@Mergifyio backport 3.3.x 3.2.x 2.14.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 #6073 done by [Mergify](https://mergify.com).

@juanlofer-eprosima juanlofer-eprosima added this to the v3.3.1 milestone Oct 7, 2025
@github-actions github-actions bot added the ci-pending PR which CI is running label Oct 7, 2025
@mergify
Copy link
Contributor Author

mergify bot commented Oct 7, 2025

🧪 CI Insights

Here's what we observed from your CI run for 689f778.

🟢 All jobs passed!

But CI Insights is watching 👀

@juanlofer-eprosima
Copy link
Contributor

@Mergifyio rebase

Signed-off-by: Juan Lopez Fernandez <juanlopez@eprosima.com>
(cherry picked from commit 81a5b12)
@mergify
Copy link
Contributor Author

mergify bot commented Oct 9, 2025

rebase

✅ Branch has been successfully rebased

@juanlofer-eprosima juanlofer-eprosima requested review from richiprosima and removed request for richiprosima October 9, 2025 06:37
Copy link
Contributor

@juanlofer-eprosima juanlofer-eprosima left a comment

Choose a reason for hiding this comment

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

LGTM, failed tests are unrelated.

@juanlofer-eprosima juanlofer-eprosima merged commit c565e11 into 3.3.x Oct 9, 2025
27 of 34 checks passed
@juanlofer-eprosima juanlofer-eprosima deleted the mergify/bp/3.3.x/pr-6073 branch October 9, 2025 14:28
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