go-libp2p
go-libp2p copied to clipboard
libp2p
libp2p implementation in Go
This PR illustrates how we could run go-tests in parallel with the unified ci. This might make CI slower though: instead of waiting for 6 runners, we'll wait for 12....
In the context of looking into https://github.com/libp2p/go-libp2p/issues/1324, clean up `TestMultiplePeers`.
Right now the connection manager has a notion of trimming excess connections when they pass the high watermark. The resource manager also blocks any connection once limits have been hit....
Currently, it waits for _any_ connection, then returns. Unfortunately, this means that if the user calls `host.NewStream(peer)` to try to get a new stream to a non-connected peer, we'll _fail_...
speed up CI
CI is taking a long time to run our builds. We should 1. split up our builds. There's no need to run `go test` and `go test -race` sequentially. These...
Not all addresses are created equal, and we should be smarter when dialing: * We should prefer IPv6 over IPv4, implementing an Happy-Eyeballs-like mechanism as described in [RFC 8305](https://datatracker.ietf.org/doc/html/rfc8305). *...
Looks like a regression. Need to investigate. https://travis-ci.com/github/libp2p/go-libp2p/builds/166912970.
Examples on how to initiate go-libp2p-resource-manager with custom limits and how to apply go-libp2p's default limits here. Should happen after: https://github.com/libp2p/go-libp2p-resource-manager/pull/48
``` === RUN TestAutoNATServiceDialRateLimiter svc_test.go:117: Dial back succeeded unexpectedly! --- FAIL: TestAutoNATServiceDialRateLimiter (0.32s)
https://github.com/libp2p/go-libp2p/runs/7060208469?check_suite_focus=true ``` === RUN TestDialSimultaneousJoin dial_test.go:584: third dial succedded; conn: dial_test.go:594: Error Trace: dial_test.go:594 Error: Received unexpected error: failed to dial 12D3KooWGEcD5sW5osB6LajkHGqiGc3W8eKfYwnJVVqfujkpLWX2: * [/ip4/127.0.0.1/tcp/49901] failed to negotiate security protocol: context...