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
Browser-to-browser connections with WebRTC are first negotiated with a transient relayed connection. bitswap protocol should not use this connection (libp2p/js-libp2p#1890).
Currently bitswap will dial a peer, possibly initiating this negotiation. It attempts to use the relayed (transient) connection to send messages but fails with CodeError: Cannot open protocol stream on transient connection.
This could be more resilient if bitswap would wait until the connection is fully upgraded or would retry the messages on the direct connection.
The text was updated successfully, but these errors were encountered:
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:
"Priority" labels will show how urgent this is for the team.
"Status" labels will show if this is ready to be worked on, blocked, or in progress.
"Need" labels will indicate if additional input or analysis is required.
Problem
Browser-to-browser connections with WebRTC are first negotiated with a
transient
relayed connection. bitswap protocol should not use this connection (libp2p/js-libp2p#1890).Currently bitswap will dial a peer, possibly initiating this negotiation. It attempts to use the relayed (
transient
) connection to send messages but fails withCodeError: Cannot open protocol stream on transient connection
.This could be more resilient if bitswap would wait until the connection is fully upgraded or would retry the messages on the direct connection.
The text was updated successfully, but these errors were encountered: