nextflow icon indicating copy to clipboard operation
nextflow copied to clipboard

A DSL for data-driven computational pipelines

Results 407 nextflow issues
Sort by recently updated
recently updated
newest added

## New feature The recent collaboration between `NCBI` and the cloud providers allows one to query the entire archive based on the metadata in AWS Athena. Here are some relevant...

kind/feature

## Bug report After a successful run of my pipeline, I am trying to clean the workspace from previous runs. I'm doing so using `nextflow clean -f -before nauseous_cajal`, which...

stale

## Bug report I am not sure if this is a bug or feature, but it's definitely worth to mention, at least on https://www.nextflow.io/blog/2019/troubleshooting-nextflow-resume.html because I think that this behaviour...

stale

## Bug report ### Expected behavior and actual behavior Versions containing dashes (`-`), such as `22.09.4-edge`, end up being reported without the dashes (`22.09.4-edge` becomes `22.09.4.edge`) ### Steps to reproduce...

## Bug report ### Expected behavior and actual behavior On a system / in an environment where (by mistake) SSL / TLS certificates are not available, running the `nextflow` script...

stale

Using nf-core pipelines as an example, by default we set `--outdir ./results` which is fine for shared file systems / HPC environments but with the growing adoption of Cloud this...

## New feature Running gcsfuse in a docker container to mount a gs bucket requires the container either to be run with --privileged, or with --device=/dev/fuse --cap-add=SYS_ADMIN for it to...

storage/gcp
stale
platform/google-lifesciences

## Bug report (input channel val field somehow is treated as path) ### Expected behavior and actual behavior (nextflow works with 50 sample, on the 51st sample, it trigger an...

stale

## Bug report Hello, From this script example: ``` vepVersionCh = Channel.from(1,2,3) process vep { label { "vep${version}" } input: val(version) from vepVersionCh """ echo ${version} """ } ``` Dynamic...

known issue
stale

## Bug report I am noticing a problem with the Nextflow-SLURM interface when processing large number of jobs. For example, I am running a workflow and have spawned ~10,000 tasks...

executor/slurm