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
Copy file name to clipboardExpand all lines: pkg/coordinator/tasks/check_consensus_proposer_duty/README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,9 @@ The `check_consensus_proposer_duty` task is designed to check for a specific pro
11
11
-**`validatorIndex`**:\
12
12
The index of a specific validator to be checked. If this is set, the task focuses on the validator with this index. If it is `null`, the task does not filter by a specific validator index.
13
13
14
+
-**`minSlotDistance`**:\
15
+
The minimum slot distance from the current slot at which to start checking for the validator's proposer duty. A value of 0 indicates the current slot.
16
+
14
17
-**`maxSlotDistance`**:\
15
18
The maximum number of slots (individual time periods in the blockchain) within which the validator is expected to propose a block. The task succeeds if a matching validator is scheduled for block proposal within this slot distance.
Copy file name to clipboardExpand all lines: pkg/coordinator/tasks/run_task_options/README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,9 @@ The `run_task_options` task is designed to execute a single task with configurab
8
8
-**`task`**:\
9
9
The task to be executed. This is defined following the standard task definition format.
10
10
11
+
-**`propagateResult`**:\
12
+
This setting controls how the result of the child task influences the result of the `run_task_options` task. If set to `true`, any change in the result of the child task (success or failure) is immediately reflected in the result of the parent `run_task_options` task. If `false`, the child task's result is only propagated to the parent task after the child task has completed its execution.
13
+
11
14
-**`exitOnResult`**:\
12
15
If set to `true`, the task will cancel the child task as soon as it sets a result, whether it is "success" or "failure." This option is useful for scenarios where immediate response to the child task's result is necessary.
13
16
@@ -20,6 +23,12 @@ The `run_task_options` task is designed to execute a single task with configurab
20
23
-**`ignoreFailure`**:\
21
24
When `true`, any failure result from the child task is ignored, and the `run_task_options` task will return a success result instead. This is useful for cases where the child task's failure is an acceptable outcome.
22
25
26
+
-**`retryOnFailure`**:\
27
+
If set to `true`, the task will retry the execution of the child task if it fails, up to the maximum number of retries specified by `maxRetryCount`.
28
+
29
+
-**`maxRetryCount`**:\
30
+
The maximum number of times the child task will be retried if it fails and `retryOnFailure` is true. A value of 0 means no retries.
31
+
23
32
-**`newVariableScope`**:\
24
33
Determines whether to create a new variable scope for the child task. If `false`, the current scope is passed through, allowing the child task to share the same variable context as the `run_task_options` task.
25
34
@@ -31,9 +40,12 @@ Default settings for the `run_task_options` task:
Copy file name to clipboardExpand all lines: pkg/coordinator/tasks/run_tasks/README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
## `run_tasks` Task
2
2
3
3
### Description
4
-
The `run_tasks` task is designed for executing a series of tasks sequentially, ensuring each task is completed before starting the next. This setup is essential for tests requiring a specific orderof task execution.
4
+
The `run_tasks` task executes a series of specified tasks sequentially. This is particularly useful for scenarios where tasks need to be performed in a specific order, with the outcome of one potentially affecting the subsequent ones.
5
5
6
6
#### Task Behavior
7
7
- The task starts the child tasks one after the other in the order they are listed.
@@ -15,6 +15,9 @@ An important aspect of this task is that it cancels tasks once they return a res
15
15
-**`tasks`**:\
16
16
An array of tasks to be executed one after the other. Each task is defined according to the standard task structure.
17
17
18
+
-**`stopChildOnResult`**:\
19
+
If set to `true`, each child task in the sequence is stopped as soon as it sets a result (either "success" or "failure"). This ensures that once a task has reached a outcome, it does not continue to run unnecessarily, allowing the next task in the sequence to commence.
20
+
18
21
-**`expectFailure`**:\
19
22
If set to `true`, this option expects each task in the sequence to fail. The task sequence stops with a "failure" result if any task does not fail as expected.
20
23
@@ -29,6 +32,7 @@ Default settings for the `run_tasks` task:
0 commit comments