-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Unsure about Connecting behaviour #105
Comments
Ideally, the |
Hello, libp2p devs from 2016/7! Just dug up this old issue :D libp2p 2020 has dial deduplication at the swarm level: https://github.com/libp2p/go-libp2p-swarm/blob/master/dial_sync.go. So goroutine |
Fix networking related test failures
migrate to standard Go tests, stop using Ginkgo
#105) * event: Add autonat events (#25) * add events for identify (#26) * implement caching for rsaKey.Bytes() * store marshalled protobuf in cache for RsaPublicKey.Bytes() * fix(crypto): fix build when openssl is enabled * add godocs to routability events. Co-authored-by: Łukasz Magiera <magik6k@users.noreply.github.com> Co-authored-by: Whyrusleeping <why@ipfs.io> Co-authored-by: Adin Schmahmann <adin.schmahmann@gmail.com> Co-authored-by: Steven Allen <steven@stebalien.com>
I'm making this issue as a note to go investigate and test what happens in the following situation:
host.Connect(C1, P)
host.Connect(C2, P)
C1
gets cancelled.does routine B error out? or does it continue trying to connect to the peer?
The text was updated successfully, but these errors were encountered: