Hey all, I've recently added the

error_retry

label to some of my modules. The heads of these modules look like this now:

process FORCE_HIGHER_LEVEL {
    tag { tile }
    label 'process_medium'
    label 'error_retry'

When linting the pipeline, every module that has the

error_retry

label produces this warning:

force-higher_level              │ modules/local/force-higher_level.nf             │ Non-standard labels found: error_retry

The

error_retry

is defined in the template's

base.config

file, so I assumed that it would be a standard label. Am I misunderstanding the usage of

error_retry

or is that a bug in

nf-core lint

?

which nf-core tools version is this ?

nf-core/tools version 2.14.1

Just pushed the changes to our fork: https://github.com/CRC-FONDA/nf-core-rangeland

nothing obviously wrong....one min...checking with another pipeline

no module in methylseq's master branch has the

error_retry

label. Adding a local module with the label to methylseq produces the same warning for me. Adding the label to a nf-core module does not produce the warning (but rather the error: "Local copy of module does not match remote") Seems to be related to local modules?

Yes, I will do that. Just confirming with some other pipelines.

not sure if we are enforcing it but, def recommend the latter structure

modules/local/force-mosaic/main.nf

as soon you will be expected to have a

tests/

sub-folder along with the main of each module