Repository navigation
fix(events): list an absent publisher's clashing assignments in the programme's order - #562
Merged
Merged
Conversation
…rogramme's order Several assignments of one meeting came back in whatever order the table returned them, so the list an absent publisher reads, and the reference suite, could change from one run to the next. They now follow the programme: the meeting's parts, then its services, each in their order.
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
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.
Fixes a random failure in the full integration run, in
assignments.reference.When an absent publisher has several clashing assignments in one meeting,
listUserConflictsInRangereturned them in whatever order the table gave. It only sorted by date, and that sort keeps whatever order it is given within a meeting. So the list the publisher reads, and the reference, could change from one run to the next. It flaked on #560's full run, in code that PR didn't touch.They now follow the programme: the meeting's parts, then its services, each by
order(id breaks ties).Verification