Skip to content
This repository has been archived by the owner on Apr 19, 2023. It is now read-only.

[SUGGESTION] Migration to Nextflow Version 20.04.1 #182

Closed
dweemx opened this issue Mar 19, 2020 · 0 comments · Fixed by #213
Closed

[SUGGESTION] Migration to Nextflow Version 20.04.1 #182

dweemx opened this issue Mar 19, 2020 · 0 comments · Fixed by #213
Assignees
Labels
enhancement New feature or request

Comments

@dweemx
Copy link
Contributor

dweemx commented Mar 19, 2020

Is your feature request related to a problem? Please describe.
No.
Migration to Nextflow Version 20.04.0

Describe the solution you'd like

include { foo; foo as bar } from "$MODULE"
  • Fixes issue with singularity where the spawned processes are not killed
  • nextflow config works from remote locations => no need for an explicit nextflow pull

Describe alternatives you've considered
/

Additional context
/

@dweemx dweemx added the enhancement New feature or request label Mar 19, 2020
@dweemx dweemx self-assigned this Mar 19, 2020
@dweemx dweemx changed the title [SUGGESTION] Migration to Nextflow Version 20.01.0 [SUGGESTION] Migration to Nextflow Version 20.01.0 Mar 19, 2020
@dweemx dweemx changed the title [SUGGESTION] Migration to Nextflow Version 20.01.0 [SUGGESTION] Migration to Nextflow Version 20.04.0 Apr 23, 2020
@dweemx dweemx changed the title [SUGGESTION] Migration to Nextflow Version 20.04.0 [SUGGESTION] Migration to Nextflow Version 20.04.1 May 13, 2020
This was referenced May 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant