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

Only add new ut_pex peers when we're not seeding #702

Merged
merged 1 commit into from Mar 29, 2016
Merged

Only add new ut_pex peers when we're not seeding #702

merged 1 commit into from Mar 29, 2016

Conversation

@feross
Copy link
Member

feross commented Mar 28, 2016

Otherwise, we get into a loop of connect, get pex messages, disconnect
because they don't have pieces we need (because we're seeding), try
connecting to the pex peers, etc. etc.

Otherwise, we get into a loop of connect, get pex messages, disconnect
because they don't have pieces we need (because we're seeding), try
connecting to the pex peers, etc. etc.
@feross feross merged commit 0ee69bc into master Mar 29, 2016
4 checks passed
4 checks passed
continuous-integration/appveyor/branch AppVeyor build succeeded
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@feross feross deleted the fix-pex branch Mar 29, 2016
@feross

This comment has been minimized.

Copy link
Member Author

feross commented Mar 29, 2016

cc @dcposch @mafintosh This seems to help the situation quite a bit!

@lock

This comment has been minimized.

Copy link

lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant
You can’t perform that action at this time.