#C02FC6VFQG1 ok now nothing is working.... I have updated nf-core version and metadenovo version and then I triend using the -c command to extend eukelele time but now I get the message below....... help: N E X T F L O W ~ version 26.04.1 WARN: Cannot read project manifest -- Cause: Config parsing failed WARN: This Nextflow version supports a new Multi-revision strategy for managing the SCM repositories, but 'nf-core/metatdenovo' is single-revision legacy strategy - Please consider to update the repository with the 'nextflow pull -migrate' command. Error nextflow.config37235:

manifest

is not defined │ 372 | \033[0;35m nf-core/metatdenovo ${manifest.version}\033[0m ╰ | ^^^^^^^^ Error nextflow.config37526:

manifest

is not defined │ 375 | afterText = """${manifest.doi ? "\n* The pipeline\n" : ""}${ma ╰ | ^^^^^^^^ Error nextflow.config37569:

manifest

is not defined │ 375 | ? "\n* The pipeline\n" : ""}${manifest.doi.tokenize(",").collect { " ╰ | ^^^^^^^^ Error nextflow.config375186:

manifest

is not defined │ 375 | doi.org/','')}"}.join("\n")}${manifest.doi ? "\n" : ""} ╰ | ^^^^^^^^ Error nextflow.config38422:

validation

is not defined │ 384 | beforeText = validation.help.beforeText ╰ | ^^^^^^^^^^ Error nextflow.config38521:

validation

is not defined │ 385 | afterText = validation.help.afterText ╰ | ^^^^^^^^^^ ERROR ~ Config parsing failed

The config file is supposed to be a text file. The errors probably indicate that there's a formatting error in the file you provided. Make sure it's just a text file. However, I've seen cases where a config file was sensitive to which characters were used as space, i.e. whitespace, tabs or something else, and how many. If I remember correctly, two spaces for each level worked in that case. In summary, if config parsing continues to fail after you've made sure it's a text file, check what type of indentation characters you use and how many.