Jorropo

Btw I get the problem you are describing *could* happen, but have you seen this in the wild ? I tried https://github.com/uber-go/mock (Uber's maintained fork) with `golang.org/x/tools v0.21.0` and it...

I've tried to repro your problem and I'm a bit confused: - libp2p is only [one of many project](https://pastebin.com/aG5A1PBK) in the module graph specifying `tools.go` and having a dependency on...

It might be worth completely reworking the transport pipeline to be bottom up instead of top down (so tls, noise, multiselect and websocket would all receive the tcp transport instead...

@wlynxg we are trying to not get into a situation where we have more than one connection in the first place. For example the dialler cancel dialling once we got...

@wlynxg I assumed too much mb. Your idea is good, multiple connections have cases where they are great indeed as you explained. The problem I have with this code is...

> However, this requires fragmentation of data packets for reliable transmission, which will increase a lot of workload ***https://github.com/libp2p/specs/issues/328 https://github.com/libp2p/specs/pull/406*** exists for theses purposes

I would like to support WASM too but I want to you know that you havn't added anything to the test suite. If we don't test WASM in CI I...

@hannahhoward I would like to merge your pull request because it fixes an issue with bitswap where opentelemetry traces between bitswap inputs are not linked with the content router however...

This is failing to build in Kubo due to https://github.com/ipfs/go-ipld-format/blob/0f7aff00f72e9dea0d9718bc0972e309ba7c3e8d/format.go#L27

What we want to do is going through trying to remove the `tests.Flaky` call from the `bitswap/...` tests and see what tests reliably pass and which one do not. Some...