Repository navigation
Allow slow 4K startup to finish within a bounded twelve-second window - #45
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 cold 4K startup can hit the current eight-second barrier while a required fourth fragment is still arriving, then fail without displaying a frame. Allow the one-shot startup reservoir up to twelve seconds from the original first-fragment entry, still clipped to the shorter HLS parent deadline. Ordinary speculation stays at eight seconds; four objects/24 MiB, serial futures, recovery headroom, authority checks, ACK ownership and retry refusal remain intact.
Add a controlled continuation with fourth completion at 8.7 seconds, absolute expiry and shorter-parent coverage. The captured WAN response was cancelled at eight seconds, so its eventual completion is unknown. Update API, integration and AI-facing documentation; physical-device and sustained playback qualification remain separate.
Validation: regression fails under the preceding policy and passes with the startup-only budget; broader swarm tests, syntax and documentation checks recorded before merge.