Max Inden
Max Inden
> I hope (after the remaining issue is solved) we can regularly test to be sure it stays stable and behaving as expected. In most implementations we run these tests...
> I tried to reproduce it locally, and it **seems** that the problem is that the rust implementation requests (and waits) for an identify stream ("/ipfs/id/1.0.0") before requesting the ping...
> Do you expect when an implementation does not support a protocol, it resets the stream immediately? It should not reset the stream. The initiator might still have other protocols...
Thank you @MarcoPolo! I am sorry for the delay. I am currently focusing on https://github.com/protocol/bifrost-infra/issues/2622. I have not forgotten about this issue.
Documenting progress thus far: > We need to use the bitrate on the receiver side. The sender can push as much data as you want, but for these measurements we...
I see your point. I am hesitant to do any math beyond a simple boxplot on the data, as that would obfuscate details. Instead I suggest to tackle the confusion...
In favor of it. A note in case we tackle this: ipv6 with Docker Compose is not as trivial as ipv4 https://docs.docker.com/config/daemon/ipv6/.
Fine by me. Likely only needed for the interoperability tests, right?
Oh, my bad. I somehow thought this issue is on the rust-libp2p repository. Don't mind me.
Hi there, Thanks for upstreaming this. In general I am not opposed to being no-std compliant, unless it adds significant overhead to the crate. Do you think it makes sense...