nextflow-io/nextflow

Add error strategy shortcuts

Open

#563 opened on 2018年1月10日

GitHub で見る
 (10 comments) (0 reactions) (0 assignees)Groovy (3,382 stars) (784 forks)batch import
good first issue

説明

The errorStrategy 'retry' implicitly terminates the execution when a task exceeds the max number of allowed retries.

There are use cases in which the user wants to ignore of finish the workflow execution. This is possible by using a dynamic error strategy (closure). However it would be useful to provide two new synthetic error strategies to simplifies the above use case, such as:

  • retryThenIgnore: task execution is retried in case of error, if the errors exceed the maximum number allowed the task is ignored by applying the ignore error strategy.
  • retryThenFinish: task execution is retried in case of error, if the errors exceed the maximum number allowed the execution is stopped by applying the finish error strategy.

コントリビューターガイド

技術スタック
なし
領域
backend
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Familiarity with Nextflow error strategiesBasic Groovy knowledge
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
40
調査方針
Examine how the existing `errorStrategy` directive processes 'retry', 'ignore', and 'finish' strategies in the Nextflow source code, likely in the workflow execution engine. The issue mentions a dynamic closure workaround, so understanding that implementation will help in adding the shortcuts. Look for classes handling task error handling, possibly in the `nextflow.processor` or similar package.
Add error strategy shortcuts · nextflow-io/nextflow#563 | Good First Issue