libp2p / libp2p/universal-connectivity
bug: webrtc connections fail after relayed connection is closed/expired
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
Users report that webrtc (brower-to-browser) connections fail after connectivity to the relay node is closed/reservation expires
Related: https://github.com/libp2p/js-libp2p-webrtc/issues/173
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by investigating the WebRTC connection lifecycle around relay-node closure and reservation expiry, then read the related libp2p/js-libp2p-webrtc issue #173 for context. Reproduce the reported failure and identify the relevant connection entry points; done means browser-to-browser connections continue to work after relay connectivity is closed or expires.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100