-
Notifications
You must be signed in to change notification settings - Fork 55
fix: non-monotonic operation order in AdLib execution context #1546
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
jstarpl
merged 10 commits into
Sofie-Automation:release53
from
nrkno:fix/resolve-timeline-wrong-time-redux
Nov 14, 2025
Merged
fix: non-monotonic operation order in AdLib execution context #1546
jstarpl
merged 10 commits into
Sofie-Automation:release53
from
nrkno:fix/resolve-timeline-wrong-time-redux
Nov 14, 2025
+529
−200
Conversation
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
ca00864 to
3ddd1fd
Compare
|
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
650087f to
26dc3ab
Compare
7 tasks
nytamin
approved these changes
Nov 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
About the Contributor
This pull request is posted on behalf of the NRK.
Type of Contribution
This is a: Bug fix
Current Behavior
We have found a issue where the timings of pieces are not monotonic.
This only affects infinite pieces, and probably only when
multiGatewayModeis enabled.How to reproduce:
In a blueprints adlibAction:
This results in a virtual piece being inserted to stop the previous infinite
OutOnShowStyleEndpiece, at timegetCurrentTime()+calculateNowOffsetLatency(this is correct).Then a pieceInstance is inserted at time
"now", which is later resolved usinggetCurrentTime().In our case, this ends up in that the virtual piece ends up after the inserted Piece, thus instantly ending it.
New Behavior
The use of
getCurrentTime()+calculateNowOffsetLatencyis abandoned altogether. A new method,getNowInPlayoutis added on thePlayoutModelthat will return monotonic timestamps for a now value, considering any latency involved. This can be sampled throughout the timeline generation process to account for any latency, but ensure that subsequent calls will not return values before previously returned.Testing
Affected areas
This PR affects the playout logic in general.
Time Frame
Other Information
Disclaimer: I have not gone through the other places where
getCurrentTime()is used, so there might be other placescalculateNowOffsetLatencyshould be used.Status