Skip to content

fix(events): list an absent publisher's clashing assignments in the programme's order - #562

Merged
mindsers merged 1 commit into
mainfrom
fix/conflicts-order
Nov 18, 2026
Merged

mindsers merged 1 commit into
mainfrom
fix/conflicts-order

Conversation

@mindsers

Copy link
Copy Markdown
Contributor

Fixes a random failure in the full integration run, in assignments.reference.

When an absent publisher has several clashing assignments in one meeting, listUserConflictsInRange returned 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

  • New integration test: one meeting's parts and services, created in an order the programme doesn't follow. It failed before the fix and passes after.
  • Every reference unchanged. The reference already expected programme order; now that order is guaranteed.
  • Unit (652 files) and integration (117 files, two full runs) suites, lint, typecheck and every architecture gate.

…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.
@mindsers
mindsers merged commit 32e1e34 into main Nov 18, 2026
7 checks passed
@mindsers
mindsers deleted the fix/conflicts-order branch November 18, 2026 22:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant