Repository navigation
Keep valid 4K startup through playlist timestamp round-off - #80
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.
Pin RelaySwarm 45616b8 so equivalent Hls.js fragment timestamps survive a playlist refresh instead of cancelling startup. The source fix accepts only capped machine-precision round-off; media identity, real geometry changes and the existing recovery/resource/deadline checks remain authoritative. Version the existing module chain and update the showcase and AI-facing docs.
Validation: one bundle build, 371/371 site tests, catalogue build and drift pass. Dependency lock and WASM are unchanged; host edits are cache-query only, and no private coordination or diagnostic code is bundled. This fixes a reproduced false cancellation and does not claim sustained 4K or phone acceptance.