Repository navigation
Make the web UI resilient to flaky networks and add a playback log - #80
Merged
Merged
Conversation
…work loss, and add a playback log
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
On mobile, brief network drops made API requests fail and left playback stalled, with no way to diagnose why. The web UI now retries transient failures, recovers playback after connectivity returns, and records a playback log.
What
useConnectivityand reworkusePlayerstream recovery so playback resumes after network loss.playbackLog.ts) shown in a new panel on the About page.useAuth, session handling, and the agent docs to match.