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
Record the parallel failure-order marker by default (phase 2 of #307) #351
#348 ships the parallel failure-order marker (durable_workflow.parallel_failure_order) as read always, write opt-in:
Worker(record_parallel_failure_order=True) or DURABLE_WORKFLOW_RECORD_PARALLEL_FAILURE_ORDER=true turns writing on.
The default is off, because published 2.20.0 and earlier cannot replay a marked run. The Server marks the workflow task replay-blocked and the run waits for repair.
Required outcome (next minor after the release that includes #348): writing defaults to on, so new runs raise an all() group's first recorded member failure by default.
Acceptance
The default flips to on. false still turns it off.
The CHANGELOG states:
the minimum worker version every worker on a task queue must run before upgrading;
The default-path fixtures (failure-order-default-first-task-sends-released-commands, parallel-group-metadata-emission and the completion-limit fixtures) are superseded properly at the next protocol version, or kept with recording explicitly set to off. They are not rewritten.
Activity
Make writing the failure-order marker opt-in (#307)