João Oliveira
João Oliveira
Hi, in the rust-libp2p community call I remarked that it was strange that `if-watch` was unmaintained, but I have since found https://github.com/mxinden/if-watch/pull/37#issuecomment-2200783907, I have also acted upon it and wrote...
will close this for now as @nazar-pc mentions it doesn't reproduce anymore. Anyone feel free to re-open if not
closed with https://github.com/libp2p/rust-libp2p/pull/5917 for `libp2p-tls` https://github.com/libp2p/rust-libp2p/pull/5448 awaiting to be merged to fix it for `libp2p-webrtc` as well
Hi, and thanks for the interest, this should be submitted at the `if-watch` repo, can you get an isolated MRE? Thanks
> What is the state of this? Hi @sirandreww-starkware which part are you asking specifically about?
Hi, The backpressure system in gossipsub was designed to prevent slow peers from potentially DOS'ing by boundlessly growing message queues. For network health, message priority is important - that's why...
no, but what would be the advantage of that?
can you elaborate on what you mean by taking care of the messages already there? Yes the vector is that, if a node's send queue grows boundlessly it eventually OOM's...
> As I think on this, I wonder if we could remove `futures-ticker` instead. It was introduced in #3973 and from my understanding it was to used as an `Interval`...
addressed with #5674