You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When connecting a js-libp2p (browser) peer and rust-libp2p peer via webrtc, data channels are no properly closing.
The first reason for that is js-libp2p never closes them to begin with. That is being addressed here: libp2p/js-libp2p#1976
The next issue is that the rust-libp2p WebRTC implementation webrtc-rs doesn't properly respond to the browsers stream reset, leaving the browser in a closing state.
I am opening this issue for visibility, and to possibly get some support with the PR reviews on these repositories.
This can be closed when bumping the dependency version.
Would you like to work on fixing this bug?
Yes
The text was updated successfully, but these errors were encountered:
Summary
When connecting a
js-libp2p
(browser) peer andrust-libp2p
peer via webrtc, data channels are no properly closing.The first reason for that is
js-libp2p
never closes them to begin with. That is being addressed here: libp2p/js-libp2p#1976The next issue is that the
rust-libp2p
WebRTC implementationwebrtc-rs
doesn't properly respond to the browsers stream reset, leaving the browser in aclosing
state.And in case of switching to
str0m
#3659, it also has the same issue:Possible Solution
I am opening this issue for visibility, and to possibly get some support with the PR reviews on these repositories.
This can be closed when bumping the dependency version.
Would you like to work on fixing this bug?
Yes
The text was updated successfully, but these errors were encountered: