From e06dc22fbc876b2b10b1baf6227b220c21885ea4 Mon Sep 17 00:00:00 2001 From: Hilary James Oliver Date: Sat, 22 Apr 2023 11:30:53 +1200 Subject: [PATCH] Update set proposal. --- docs/proposal-cylc-set.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/proposal-cylc-set.md b/docs/proposal-cylc-set.md index 4a002b6f..7cc16d5e 100644 --- a/docs/proposal-cylc-set.md +++ b/docs/proposal-cylc-set.md @@ -43,11 +43,13 @@ This may be a matter of opinion, but I prefer the latter. - It is not equivalent to setting the parent output, unless the task is an only child. - It is not equivialent to triggering, unless the task has only one unsatisfied prerequisite. + - DEFAULT: set all prerequisites (this would be equivalent to trigger) 2. Force set specified **outputs** of a target task. - This contributes to the task's completion, and sets the corresponding prerequisites of child tasks. - Set *implied outputs* as well (see command help below). - If the `succeeded` or `failed` outputs are set, disable automatic retries. + - DEFAULT: set all required outputs. 3. Force expire tasks. - Expire means "we no longer need to run (or rerun) this task".