-
Notifications
You must be signed in to change notification settings - Fork 43
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
feat: spec test for connection manager #1417
Conversation
size-limit report 📦
|
this.libp2pComponents.peerStore.addEventListener( | ||
"peer", | ||
this.libp2pComponents.addEventListener( | ||
"peer:discovery", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
haha, good thing we're adding tests :)
); | ||
}); | ||
|
||
it("should be called for every peer with PEER_EXCHANGE tags", async function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we checkng that peer exhcange peers are not limited by the max bootstrap peers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, that is covered by the "should be called for every peer with PEER_EXCHANGE tags"
scenario:
it("should be called for every peer with PEER_EXCHANGE tags", async function () { |
This PR addresses #1413:
Cases covered:
peer:discovery
event emitter when fired triggers a dial attempt for the peermaxBootstrapPeersAllowed
flag is reachedNotes
Please mention any test cases you think should be added/have been missed for ConnectionManager