Skip to content

fix: Cancel update before schedule an update after fetchAndAppend #8878

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 2 commits into from
Jul 17, 2025

Conversation

avelad
Copy link
Member

@avelad avelad commented Jul 16, 2025

onSegmentAppended occurs before scheduling the update, but in that case we can change streams (eg: L3D) and cause an update, with this change we avoid having two updates at the same time.

@avelad avelad requested a review from a team July 16, 2025 16:05
@avelad avelad added type: bug Something isn't working correctly priority: P1 Big impact or workaround impractical; resolve before feature release labels Jul 16, 2025
@avelad avelad added this to the v4.16 milestone Jul 16, 2025
@joeyparrish
Copy link
Member

Could you put some info about what visible behavior this fixes? Either in the title, if it's short, or in the description, if it's not? Would be more useful in change logs that way.

@shaka-bot
Copy link
Collaborator

Incremental code coverage: 100.00%

@avelad avelad merged commit e65c3c6 into shaka-project:main Jul 17, 2025
30 of 32 checks passed
@avelad avelad deleted the streaming-engine-cancelUpdate branch July 17, 2025 08:38
avelad added a commit that referenced this pull request Jul 21, 2025
)

onSegmentAppended occurs before scheduling the update, but in that case
we can change streams (eg: L3D) and cause an update, with this change we
avoid having two updates at the same time.
avelad added a commit that referenced this pull request Jul 21, 2025
)

onSegmentAppended occurs before scheduling the update, but in that case
we can change streams (eg: L3D) and cause an update, with this change we
avoid having two updates at the same time.
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