nextflow-io/nextflow

Add error strategy shortcuts

Open

#563 建立於 2018年1月10日

在 GitHub 查看
 (10 留言) (0 反應) (0 負責人)Groovy (3,382 star) (784 fork)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
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.