-
Notifications
You must be signed in to change notification settings - Fork 22
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
(cont) fix: use floodsub events to simplify discovery #200
Conversation
I think this approach of explicitly ending the protocol handlers when the collaboration shuts down makes sense, it's more reliable that way. In the collaboration |
By the way I love the branch name, it sounds like I've discovered something very important 👍 |
Once the connections issue is resolved we should merge in the resultant version of libp2p: https://github.com/libp2p/js-libp2p-switch/issues/288 |
Quick FYI: I'm working on checking out some test failures I'm observing on this branch (probably not related). |
Ok thanks for the heads up. I realized I need to rethink the way ring management and redials work - it's too aggressive in removing peers from the ring, and is trying too many times to reconnect to nodes that go down. I will clean it up in the next couple of hours. |
I made ring removal less aggressive. There are still a couple of test failures, although they don't appear t to fail consistently |
We should also make sure libp2p/js-libp2p-floodsub#63 is included because it sometimes causes the tests to fail. |
7909024
to
359b075
Compare
@dirkmc this is a failure I'm getting frequently in my test runs (fresh install): |
Me too, it’s coming from floodsub. I’ll take a look
…On Thu, Dec 13, 2018 at 3:29 AM Pedro Teixeira ***@***.***> wrote:
@dirkmc <https://github.com/dirkmc> this is a failure I'm getting
frequently in my test runs (fresh install):
[image: 1__bash]
<https://user-images.githubusercontent.com/47910/49925526-28160b80-feb1-11e8-94dd-264a7ce3a2ed.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#200 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKUpGQzO_-0FERnfulxJ8rrzjXAgipfks5u4g_ZgaJpZM4ZNDPi>
.
|
Fix in libp2p/js-libp2p-floodsub#65 |
b6df59f
to
7f1ebab
Compare
Ok @pgte between your fixes and my fixes the tests are now passing 🎉 The outstanding issues I found in the course of this PR are:
These were already issues before I started working on this PR, although it would be nice to have them as part of the PR. What do you think? |
It would simplify connection management a lot if we could specify to libp2p on hang up that we only want to hang up outbound connections. I created an issue on libp2p: libp2p/js-libp2p#299 |
@dirkmc for me the tests pass consistently. What do you say about merging this into master and talking about future work on this area (discovery, membership, connection management) on other issues? |
Sounds good, let’s do it!
…On Wed, Dec 19, 2018 at 7:26 AM Pedro Teixeira ***@***.***> wrote:
@dirkmc <https://github.com/dirkmc> for me the tests pass consistently.
What do you say about merging this into master and talking about future
work on this area (discovery, membership, connection management) on other
issues?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#200 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKUpCv3ghFqaN7WSEP9CaRe1q49ResGks5u6jCEgaJpZM4ZNDPi>
.
|
Move connection management into one place Ensure peer interest discovery completes
Continued from #176