I think we have to be careful with using custom functions in config files. See https://github.com/nextflow-io/nextflow/issues/870#issuecomment-441100071. 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.
We can hopefully ditch check_max() in the near future and make use of native Nextflow functionality, see https://github.com/nextflow-io/nextflow/issues/640 - that is the ideal way to solve this issue 😉
I think we have to be careful with using custom functions in config files. See https://github.com/nextflow-io/nextflow/issues/870#issuecomment-441100071. 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 innextflow.config
too to fix this too.See https://github.com/nf-core/rnaseq/pull/701#discussion_r725950036