Tiny change forcing a tool to always only use 1 CP...
# request-reviewj
James Fellows Yates
04/10/2026, 1:37 PMTiny change forcing a tool to always only use 1 CPUs: https://github.com/nf-core/createtaxdb/pull/161
š 1
m
Maxime Garcia
04/10/2026, 1:40 PMwhy no process_single?
j
James Fellows Yates
04/10/2026, 1:40 PMOH YEAH
James Fellows Yates
04/10/2026, 1:41 PMAh because it was specified as
process_longJames Fellows Yates
04/10/2026, 1:41 PMwhcih si also valid
James Fellows Yates
04/10/2026, 1:42 PMCan I put two labels š¤
m
Maxime Garcia
04/10/2026, 1:43 PMyeah
Maxime Garcia
04/10/2026, 1:43 PMthey are labels
j
James Fellows Yates
04/10/2026, 1:44 PMBut I mean in the nf-core specs we allow it?
m
Maxime Garcia
04/10/2026, 1:44 PMyes
j
James Fellows Yates
04/10/2026, 1:44 PMoh no you're going to make me topic update evertyhing š¢
James Fellows Yates
04/10/2026, 1:44 PMOk I willd othat later, Teo pick-up no
š 1
m
Maxime Garcia
04/10/2026, 1:44 PMj
James Fellows Yates
04/11/2026, 5:03 AMActually, no it is not allowed;
ā metacache/build ā modules/nf-core/metacache/build/main.nf ā process_standard_label: Conflicting process labels found: process_single,process_long ā
ā āµ āµ ā
James Fellows Yates
04/11/2026, 5:03 AMimage.png
m
Maxime Garcia
04/11/2026, 7:45 AMMeh, just a warning
j
James Fellows Yates
04/11/2026, 7:55 AMI switched to prpcess_single anyway
š 1
2 Views