Skip to content
This repository has been archived by the owner on Aug 23, 2020. It is now read-only.

Fix: prevent self initialized connection being removed from reconnect pool too early #1506

Merged
merged 1 commit into from
Jul 10, 2019

Conversation

luca-moser
Copy link
Member

Description

If we initialize a connection to a neighbor ourselves, we should not remove that URI from the reconnect
pool up on the initialized (but not handshaked) connection, because it will lead to the node
not retrying a reconnect attempt in case the handshaking/read op. was faulty.

Type of change

  • Bug fix (a non-breaking change which fixes an issue)

Checklist:

  • My code follows the style guidelines for this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • New and existing unit tests pass locally with my changes

if we init. a conn. ourselves, we should not remove that URI from the reconnect
pool up on the initialized (but not handshaked!) connection, because it will lead to the node
not retrying a reconnect attempt in case the handshaking/read op. was faulty.

Signed-off-by: Luca Moser <moser.luca@gmail.com>
@luca-moser luca-moser changed the title fixes self init. conn. being removed from reconnect pool too early Fix: prevent self initialized connection being removed from reconnect pool too early Jul 10, 2019
@luca-moser luca-moser changed the base branch from release-v1.8.0 to dev July 10, 2019 09:26
@GalRogozinski
Copy link
Contributor

GalRogozinski commented Jul 10, 2019

Fixes #1507

@GalRogozinski GalRogozinski merged commit 5d0f4b7 into iotaledger:dev Jul 10, 2019
@jakubcech jakubcech mentioned this pull request Aug 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants