Thomas Eizinger
Thomas Eizinger
> I think long term this is something we should be doing. I am not yet sure on whether the current implementation allows collaborative usage of these limits across `ConnectionHandler`...
Setting to draft until we reach a decision.
That is a fair point, thanks for bringing this up! If we want features to only be additive but still allow the user to control the runtime, then I think...
Updated the PR description with an implementation plan.
This is actually mostly complete. I'll open a new issue for the more type-safe API to create a `Swarm` with a properly set task executor.
Done here https://github.com/libp2p/rust-libp2p/issues/3068.
> It might be a good idea to record this as a metric, and make this delay configurable. An operator may want to alert when this happens since it may...
The error is already reported as of today. Unless another sub-task is woken, this shouldn't result in a busy loop?
I had a play around with this and pushed a little test harness with a docker container to test the behaviour for when we run out of file descriptors. In...
> > In the current implementation, the error is already returned but it is a busy loop. Can we perhaps change the implementation that, once we return this particular error...