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

Feature/follow up/discard unreachable shm locators #5126

Closed

Conversation

Mario-DL
Copy link
Member

@Mario-DL Mario-DL commented Aug 2, 2024

Description

Follow up of #5118

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)
  • 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.
  • 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.

EduPonz and others added 20 commits July 30, 2024 20:31
…ransports until one reports locator reachability

Signed-off-by: eduponz <[email protected]>
…m non-local ports, and shm local ports that cannot open to write

Signed-off-by: eduponz <[email protected]>
Signed-off-by: elianalf <[email protected]>
…yte because the first is used for unicast info

Signed-off-by: elianalf <[email protected]>
@Mario-DL Mario-DL added this to the v3.0.1 milestone Aug 2, 2024
@github-actions github-actions bot added ci-pending PR which CI is running labels Aug 2, 2024
@MiguelCompany MiguelCompany modified the milestones: v3.0.1, v3.0.2 Sep 4, 2024
@MiguelCompany MiguelCompany added to-do needs rebase and removed ci-pending PR which CI is running labels Oct 2, 2024
@MiguelCompany MiguelCompany removed this from the v3.0.2 milestone Oct 2, 2024
@MiguelCompany MiguelCompany added this to the v3.1.0 milestone Oct 2, 2024
@rsanchez15
Copy link
Contributor

We were closing this PR since we decided to follow a different approach.

@rsanchez15 rsanchez15 closed this Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants