Skip to content

fix: Live to VOD discards the wrong segments when crossBoundaryStrategy is not KEEP #8863

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 10, 2025

Conversation

matvp91
Copy link
Member

@matvp91 matvp91 commented Jul 10, 2025

Due to not setting the boundaryEnd for the last period, we ensure we do not discard the wrong segments in a live to VOD situation (where a boundaryEnd becomes available mid stream).

The same applies in live, when a period ends and a new period starts. The previous one will now have a boundaryEnd, the new one does not.

Co-authored-by: @avelad

@matvp91 matvp91 changed the title fix: Live to VOD discards the wrong segments when crossBoundaryStrategy is RESET fix: Live to VOD discards the wrong segments when crossBoundaryStrategy is not KEEP Jul 10, 2025
@avelad avelad requested review from avelad and tykus160 July 10, 2025 09:50
@avelad avelad added type: bug Something isn't working correctly priority: P1 Big impact or workaround impractical; resolve before feature release labels Jul 10, 2025
@avelad avelad added this to the v4.16 milestone Jul 10, 2025
@shaka-bot
Copy link
Collaborator

shaka-bot commented Jul 10, 2025

Incremental code coverage: 100.00%

@avelad avelad merged commit 731c4f1 into shaka-project:main Jul 10, 2025
29 of 32 checks passed
avelad added a commit that referenced this pull request Jul 11, 2025
avelad pushed a commit that referenced this pull request Jul 15, 2025
…gy is not KEEP (#8863)

Due to not setting the `boundaryEnd` for the last period, we ensure we
do not discard the wrong segments in a live to VOD situation (where a
boundaryEnd becomes available mid stream).

The same applies in live, when a period ends and a new period starts.
The previous one will now have a boundaryEnd, the new one does not.

 Co-authored-by: @avelad
avelad added a commit that referenced this pull request Jul 15, 2025
avelad pushed a commit that referenced this pull request Jul 15, 2025
…gy is not KEEP (#8863)

Due to not setting the `boundaryEnd` for the last period, we ensure we
do not discard the wrong segments in a live to VOD situation (where a
boundaryEnd becomes available mid stream).

The same applies in live, when a period ends and a new period starts.
The previous one will now have a boundaryEnd, the new one does not.

 Co-authored-by: @avelad
avelad added a commit that referenced this pull request Jul 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: P1 Big impact or workaround impractical; resolve before feature release type: bug Something isn't working correctly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants