Hello all - I'm having an issue with my custom config file where I rewrite the process labels (medium, large, etc.) but also have a couple of custom based 'withName' resource allocations as well. It worked with an older version of the rnaseq pipeline when I ran it a couple months ago (3.14.0) but somehow my tasks now are prioritizing the withLabel allocations over the withName more specific ones. Example, medium is vCPU 4 memory 12 but in withName, I give a certain task vCPU 4 memory 22, and in AWS Batch I see that the container for the task takes the 12. I've checked the nextflow logs and it has 'withLabel: Medium matches' the task, then the following line is 'withName matches' the same task, so I assumed it would've taken the withName? This feels unrelated, but based on what I've read the check_max function is being deprecated, and I do still have it in my config file. Will try taking it out, but doesn't seem connected so wanted to see if anyone else has had this issue.
Update: tried taking out check_max, still running into the same issue. Example of what I mean in the nextflow log:
Oct-16 14
4047.415 [main] DEBUG nextflow.script.ProcessConfig - Config settings
withLabel:process_high
matches labels
process_high
for process with name NFCORE_RNASEQ
RNASEQFASTQ_QC_TRIM_FILTER_SETSTRANDEDNESS
FASTQ FASTQC UMITOOLS TRIMGALORETRIMGALORE
Oct-16 14
4047.425 [main] DEBUG nextflow.script.ProcessConfig - Config settings
withName:.*:FASTQ_FASTQC_UMITOOLS_TRIMGALORE:TRIMGALORE
matches process NFCORE_RNASEQ
RNASEQFASTQ_QC_TRIM_FILTER_SETSTRANDEDNESS
FASTQ FASTQC UMITOOLS TRIMGALORETRIMGALORE