Repository navigation
Keep replays following and export local playback reports - #54
Merged
Merged
Conversation
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.
A replay could spend twelve seconds chasing the advancing room clock even after its current position had enough decoded video to continue. Existing playback can now resume from that safe buffer while keeping the normal buffered room correction armed. Cold joins still wait for fresh room headroom; playback remains at1x, and real waits remain counted.
Playback details also offers Save/Share report for real-device diagnosis when remote inspection is unavailable. The local report keeps at most240 observations at one-second intervals, including actual frames, dimensions, buffers, stalls, verified peer/upload bytes, library/engine version and selected candidate-type/relay-protocol enums. It omits network addresses, SDP, peer identities, keys and credentials; sharing is user-triggered and no report is uploaded automatically. The existing stats tick supplies samples without another timer or network collector.
Validation: site build and all260 Node tests pass; focused replay/report tests pass; Chrome Blob download parses correctly and the share fixture receives the same sanitized file without pausing or seeking playback. Cache tags and maintained docs/LLM text are updated. Actual iPhone ShareSheet/long playback and sustained cold-cache4K peer contribution remain separate acceptance work; this does not claim those gates passed.