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 BBC
Type of Contribution
This is a: Feature / Tech stack update
New Behavior
This updates meteor to 2.16 and replaces existing uses of mongo collection
observe
andobserveChanges
methods withobserveAsync
andobserveChangesAsync
.These changes are not necessary for 2.16, but are preperation for meteor 3.0 that is possible to do in 2.16
A couple of uses of
waitForPromise
have been replaced with native promises.This also fixes some concerns I have with some of the
*Observer
classes. I have concerns about leaks if they are in the middle of executing whilestop()
is called, to mitigate this I have given each of them a#disposed
property which allows various callbacks to know they have been disposed and make sure they don't semi-restart themselves afterstop()
is called.The most visible scenario of this is
StudioObserver
, where if stop was called while itsRundownsObserver
was being reconstructed, then thatRundownsObserver
would be leaked.There was also an issue with some of the debounces, where there could be concurrent executions of them in different fibers if the execution took longer than the debounce time. A new helper has been written and used to mitigate this
PromiseDebounce
.I suspect there were also other places of potential leaks, when multiple mongo observers were setup and if one of them threw and error the ones which succeeded would be leaked. The
waitForAllObserversReady
handler has been added to handle this safely.Testing
The publications themselves don't have any test coverage, but tests have been added for newly added helper code.
I have done some testing with light usage of Sofie, using playout-gateway, package-manager and input-gateway and haven't noticed anything wrong. More extensive testing will be performed, but I think that an important part of that is to put it in front of devs while working on other features.
Affected areas
This PR affects the publications in general.
Time Frame
Other Information
Status