Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Avoid using custom functions in config files #1287

Open
drpatelh opened this issue Oct 11, 2021 · 1 comment
Open

Avoid using custom functions in config files #1287

drpatelh opened this issue Oct 11, 2021 · 1 comment
Labels
template nf-core pipeline/component template

Comments

@drpatelh
Copy link
Member

I think we have to be careful with using custom functions in config files. See nextflow-io/nextflow#870 (comment). When running NF on Kubernetes this causes issues with the way the configs are resolved. I have been trying to find another solution to using the check_max function in nextflow.config too to fix this too.

See nf-core/rnaseq#701 (comment)
@drpatelh drpatelh mentioned this issue Oct 11, 2021
Closed
11 tasks
@maxulysse maxulysse reopened this Dec 8, 2021
blahah pushed a commit to awesome-bio/rnaseq that referenced this issue Feb 11, 2022
Remove check_max
614e1bb 
kuberun doesn't support custom functions directly in config files

See nf-core/tools#1287
@ewels
Copy link
Member

ewels commented Apr 13, 2022

We can hopefully ditch check_max() in the near future and make use of native Nextflow functionality, see nextflow-io/nextflow#640 - that is the ideal way to solve this issue 😉

@ewels ewels added template nf-core pipeline/component template and removed DSL2 v2.0 labels Apr 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
template nf-core pipeline/component template
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ewels @maxulysse @drpatelh