Darius Clark
Darius Clark
I see it was merged so ill would like to tackle this one (will do the other one in a separate pr if nobody else wish to do it)
Hmm the last time ive ran libp2p on ios I never seen this error, though it been awhile. Could you describe your building environment like the version of macos youre...
Sounds almost related to https://github.com/libp2p/rust-libp2p/issues/4917 (since the timout was reduced in https://github.com/libp2p/rust-libp2p/pull/4965) but sounds much deeper. I noticed something similar while connected with just quic back then but only assume...
Have this ever been reproduced upstream yet? Interesting to know if this is something within libp2p-quic or quinn.
@julienmalard could you provide some logs?
I think the solution for now (at least for me and my use case) would be to use the following settings ``` quic_config.max_idle_timeout = Duration::from_millis(300); quic_config.keep_alive_interval = Duration::from_millis(100); ``` so...
Any updates to this @justcode740?
@blacktoast are you still interested in tackling this issue?
While its possible to get around this by generating the cert outside of the behaviour, i think until ring does ever support RFC6979, we should probably do a workaround, though...
A default of 10 seconds may be enough to accommodate majority of the protocols, but setting to 30 seconds may be the best balance in my opinion