Fix: segment not found issues (SOFIE-3626) #1325
Merged
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 experienced various issues in production related to error messages of the
Segment "xyz" not found
type.While we haven't confidently identified the core issue we have found a few potential problems introduced in release51.
Fixes
previous
Part in Sofie, thesyncChangesToPartInstances
failed because the Segment of the previous PartInstance was not found.The fix: Include previous PartInstance in the orphan-Segment-check, so that the Segment will now be orphaned instead of removed.
updatePartInstancesSegmentIds
method where the new ids are to be synced to the PartInstances, that has now been fixed.Testing
Affected areas
Time Frame
This Bug Fix is critical for us, we till merge this asap.
Other Information
Status