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.

Sign up for GitHub

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

Jump to bottom

Handle multiple connections better. #40

Closed
Stebalien opened this issue Oct 14, 2017 · 1 comment
Closed

Handle multiple connections better. #40

Stebalien opened this issue Oct 14, 2017 · 1 comment
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@Stebalien
Copy link
Member

We can end up with multiple connections to the same peer so we should handle them better. Currently, if two peers connect to each other at the same time, they can end up not communicating.
@Stebalien Stebalien mentioned this issue Oct 14, 2017
Merged
@upperwal upperwal mentioned this issue Nov 8, 2018
Open
@daviddias daviddias added the kind/bug A bug in existing code (including security flaws) label Mar 25, 2020
@vyzo
Copy link
Collaborator

vyzo commented Mar 25, 2020

This has been addressed in #132.

@vyzo vyzo closed this as completed Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug A bug in existing code (including security flaws)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vyzo @Stebalien @daviddias