tiny-pilot / tiny-pilot/tinypilot
WebRTC frontend: revisit error handling
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
With Janus/WebRTC we have insight into the internal server state, so in contrast to the MJPEG stream we can detect and distinguish error cases. As @jdeanwallace mentioned in https://github.com/tiny-pilot/tinypilot/pull/943#pullrequestreview-924812296, there are different points of failures in the chain.
So we should investigate which failure scenarios are likely for us, and how we go about them if they happen. Potential mitigations would be:
- Log errors to the browser console
- Try to recover automatically
- Display an error notification to the user
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
Start by reviewing the WebRTC frontend failure points discussed in pull request #943 and identify the likely scenarios in the connection chain. Determine which cases need console logging, automatic recovery, or user-visible notifications; the work is done when the scenarios and corresponding handling are implemented.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100