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

LiveSegmentIndex should recover from segment exhaustion more gracefully. #140

Closed
tdrews opened this issue Jul 28, 2015 · 0 comments
Closed
Assignees
Labels
status: archived Archived and locked; will not be updated type: bug Something isn't working correctly type: code health A code health issue
Milestone

Comments

@tdrews
Copy link
Contributor

tdrews commented Jul 28, 2015

If the seek start time surpasses the seek end time LiveSegmentIndex will clamp the seek end time to the seek start time. However, if additional segments become available then the seek end time remains clamped to the seek start time unnecessarily. This is a somewhat rare case, but ideally LiveSegmentIndex should reset it's seek window when this occurs.

@tdrews tdrews added type: code health A code health issue medium? labels Jul 28, 2015
@tdrews tdrews added the type: bug Something isn't working correctly label Aug 6, 2015
@joeyparrish joeyparrish added this to the Future milestone Sep 1, 2015
@TheModMaker TheModMaker self-assigned this Oct 8, 2015
@joeyparrish joeyparrish modified the milestones: v1.6.0, Future Oct 9, 2015
@shaka-project shaka-project locked and limited conversation to collaborators Mar 22, 2018
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: archived Archived and locked; will not be updated type: bug Something isn't working correctly type: code health A code health issue
Projects
None yet
Development

No branches or pull requests

4 participants