-
Notifications
You must be signed in to change notification settings - Fork 42
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
explicit usage of libp2p.dial()
/libp2p's autodial
#1117
Comments
Are you sure? I believe this was removed in 0.40.0 as documented in: https://github.com/libp2p/js-libp2p/blob/master/doc/migrations/v0.39-v0.40.md#autodial If you remove js-waku/packages/core/src/lib/waku.ts Line 140 in 0b08320
Does it still auto dial? |
Yes - I've been able to confirm the libp2p autodials discovered nodes by default as can be seen by the logs also:
and autodial attempts:
|
right. Thank you for this investigation. Which means the current dialign we do is useless. We should probably remove our manual dial. It would also explain why In short, I agree with the proposed solution of this ticket as a first step. But, we will change that when tackling #914 so we have more fine control on connection and peer management. |
Sounds good. I have addressed this issue here #1118 |
The inconsistency is also being confirmed here: libp2p/js-libp2p#1397 (comment) |
Update: It is concluded that libp2p by default autodials until |
This issue will be closed with the linked PR merge. |
which one is the linked PR? |
the one linked is updated: #1135 |
This is a change request
Problem
We currently use
libp2p.dial()
to dial every one we discover. However, libp2p by default autodials to all nodes. (https://github.com/libp2p/js-libp2p/blob/master/doc/PEER_DISCOVERY.md)The question now is:
Proposed Solutions
Delete the usage of
libp2p.dial()
and let libp2p auto conectNotes
I'm not entirely sure if this is a good diea is why I haven't opened a PR for it yet, but just something that might open a discussion to help understand things better. (especially since we're considering a peer management overhaul)
The text was updated successfully, but these errors were encountered: