You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
all-group after select() with an open or cancelled loser gets the loser's sequence as its base #350
Found by the independent review of #348 and reproduced on published 2.19.1 and #348's head. The Server was built from server main 52e3ec00 (PHP stack, docker-compose.test.yml).
Problem 1: an all-group right after select() never schedules, and the run hangs.
Adding any durable step between the select and the group (for example yield ctx.start_timer(1)) avoids this.
Problem 2: cancelling a select loser after an all-group fails replay.
Same shape, with a spacer timer before the group:
Catch the group failure.
yield slow.cancel().
Schedule a compensation.
The task that sends cancel_selection_operation and the compensation succeeds. The next task's replay fails with NonDeterministicReplayError at workflow sequence 2, which is the cancelled loser: it is matched against activity:m0. This happens on both 2.19.1 and #348's head.
Likely cause (not yet confirmed)._annotate_parallel_commands in src/durable_workflow/workflow.py (main c593df8, around line 6877) takes candidates[0].workflow_sequence as a new group's base whenever unconsumed recorded steps exist. A select loser that is open or cancelled is still such a step, so the group's base becomes the loser's sequence. In problem 1, _group_is_open then sees that sequence as already recorded and sends nothing (#338's no-resend rule). Problem 2 looks like the same misbinding on replay.
Acceptance
A list group yielded right after a select() with an open or cancelled loser schedules at the next free sequence.
A cancelled loser replays without nondeterminism.
Replay regression fixtures for both cases, recorded on a Server.
Existing histories that used a spacer step replay unchanged.
Further case from the #348 re-review: a list group written immediately after a select(), or immediately after an update is applied, takes a base sequence that collides with an already-recorded step. On published 2.19.1 the group is then never scheduled and the run hangs. The acceptance criteria should cover both positions: directly after a select() with an open or cancelled loser, and directly after an applied update.
Activity
Gate first-recorded-failure selection on a per-run marker (#307)
rmcdaniel commentedon Nov 19, 2026
Further case from the #348 re-review: a list group written immediately after a
select(), or immediately after an update is applied, takes a base sequence that collides with an already-recorded step. On published 2.19.1 the group is then never scheduled and the run hangs. The acceptance criteria should cover both positions: directly after aselect()with an open or cancelled loser, and directly after an applied update.