Open
Conversation
Baraujo25
force-pushed
the
JMETER-BZM-HLS-3.3.0
branch
from
d55e984 to
6ff2d66
Compare
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
1 participant
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.
What's new
Build on every push, JMeter compatibility matrix (several JMeter versions + optional BlazeMeter cloud Taurus run), master/slave integration test, pinned Taurus/urwid to avoid upstream resolver breakages, JMeter and artifact caching
More correct dynamic manifest refresh (wait uses the sampler clock, refresh when the MPD is exhausted), and more precise segment timeline math (large startNumber / SegmentTimeline / presentationTimeOffset after refresh)
Optional “Start from live edge” for live/EVENT playlists (skips to near the live window; VOD unchanged; UI disabled for MPEG-DASH)
What's Changed
Full Changelog: Blazemeter/HLSPlugin@v3.2.1...v3.3.0