Hi all, I'm trying to build a new nextflow_schema.json but I've got that cryptic (to me) error at startup when 'validateParameters':

Failed: Schema [<https://harrel.dev/dff6d140>] failed to validate against meta-schema [<https://json-schema.org/draft/2020-12/schema>]
        exit status : null
        
ERROR ~ Schema [<https://harrel.dev/dff6d140>] failed to validate against meta-schema [<https://json-schema.org/draft/2020-12/schema>]

in nextflow.log:

dev.harrel.jsonschema.InvalidSchemaException: Schema [<https://harrel.dev/dff6d140>] failed to validate against meta-schema [<https://json-sche>>
        at dev.harrel.jsonschema.MetaSchemaValidator$DefaultMetaSchemaValidator.validateSchema(MetaSchemaValidator.java:49)
        at dev.harrel.jsonschema.JsonParser.validateAgainstMetaSchema(JsonParser.java:153)
        at dev.harrel.jsonschema.JsonParser.parseRootSchemaInternal(JsonParser.java:58)
        at dev.harrel.jsonschema.JsonParser.parseRootSchema(JsonParser.java:29)
        at dev.harrel.jsonschema.Validator.registerSchema(Validator.java:75)
        at dev.harrel.jsonschema.ValidatorFactory.validate(ValidatorFactory.java:230)
        at dev.harrel.jsonschema.ValidatorFactory.validate(ValidatorFactory.java:214)

I work behind a proxy. If that's the origin or the error, is there a way to skip that part of the schema validation ?

That "harrel.dev" url goes nowhere, not sure where exactly it's from. AFAIK there is no way to skip validating the schema against the parent metaschema, it's a fundamental part of the validation.

@Arthur thank , that was helpful. In the end, running nfcore-tools+lint was more explanatory than the NF message above.

It's strange though since the

<http://harrel.dev|harrel.dev>

tooling contains a cache of the parent metaschema so it shouldn't try to fetch the original one

I'm guessing from Pierre's comment that his schema was borked in some way?

Yeah that might be the case, maybe removing and redownloading the cached plugin will work?

yes, there was an error in my json

You can use JSON schema linters or the vscode extension to prevent having issues in your schema

@Nicolas Vannieuwkerke thanks Nicolas, the 'lint' is now integrated in my workflow.

Awesome! 🎉