tiny-pilot / tiny-pilot/tinypilot
WebRTC frontend: automatically reconnect after network interruption
Open
Nobody has claimed this yet.
enhancement
medium
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
Not sure this will be a common problem, but in case the stream connection interrupts, the WebRTC frontend wouldn’t automatically re-connect.
But we can probably catch the error event and then implement a periodic retry, for example.
Contributor guide
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
The issue identifies the WebRTC frontend but names no files, tests, or entry points. Locate the frontend's WebRTC connection and error handling, then determine how an interruption is detected and how periodic retries should behave. Done means the stream reconnects automatically after a network interruption.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100