fix(Core/Publications/Device Triggers): Device Action Studio Context gets lost, Adlib previews are unstable (SOFIE-3638) #1334
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
Given a specific set of conditions and user actions, Sofie Core log starts showing
Undefined Device Trigger context for studio
, and Device Trigger actions stop working until a reactivation/rundown reload. Also, some AdLib previews would "go away" during Rundown Activation/Reactivation, leaving these buttons "blank" in Input Gateway.New Behavior
Device Trigger Actions publications were rebuilt using the Collections promise API, solving the described problem. The root of the problem was that Fibers were getting in the way and making code that was assumed to work in sequence work in parallel. By employing Promises, much of the code has been parallelized, resulting in - what feels like - a very consistent experience at the Input Gateway level.
Testing
Affected areas
Time Frame
This Bug Fix is critical for us, please review and merge it as soon as possible.
Other Information
Status