Skip to content
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

fix: Fix duplicate init segment download when using startAtSegmentBoundary #6479

Merged
merged 2 commits into from Apr 26, 2024

Conversation

avelad
Copy link
Collaborator

@avelad avelad commented Apr 25, 2024

Fixes #5420

@avelad avelad added type: bug Something isn't working correctly priority: P2 Smaller impact or easy workaround labels Apr 25, 2024
@avelad avelad added this to the v4.8 milestone Apr 25, 2024
@shaka-bot
Copy link
Collaborator

Incremental code coverage: 93.55%

@avelad avelad merged commit da7863d into shaka-project:main Apr 26, 2024
12 of 15 checks passed
@avelad avelad deleted the duplicate-init-segment branch April 26, 2024 06:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: P2 Smaller impact or easy workaround type: bug Something isn't working correctly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

'streaming.startAtSegmentBoundary' makes player to download initialization segment twice
3 participants