nextflow-io/nextflow

Add error strategy shortcuts

Open

#563 opened on Jan 10, 2018

View on GitHub
 (11 comments) (0 reactions) (0 assignees)Groovy (784 forks)batch import
good first issue

Repository metrics

Stars
 (3,382 stars)
PR merge metrics
 (Avg merge 16d 9h) (54 merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Study the existing error strategy implementation in Nextflow, specifically the retry strategy and how ignore and finish are applied. Then implement two new strategies that extend the retry behavior with these fallbacks.
Tech stack
groovy
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Nextflow
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50