Hey guys, the fact that an

--outdir

on Azure storage needs to have a slash appended (whereas a local dir does not) definitely seems like a bug to me. Does the pipeline have anything to do with this, or is this handled by Nextflow (since the pipeline ideally should be agnostic of the storage medium)?

I'm guessing it's a generic thing- am I right @Adam Talbot?

It's a bug in nf-schema. It used to be a bug, then I fixed it, now it's back. It's because Azure blob storage is absolutely terrible and has no way of terrible and doesn't have a way of distinguishin directories vs files @Nicolas Vannieuwkerke can we merge my PR? I won't have time to test it for ages but the tests pass 🤷

So the problem is actually in the nf-azure plugin. You can solve this by always adding a

/

to directories. The workaround in nf-schema is nice but should not be the permanent option here as it basically disables validation again. I'll take a look at merging it next week. I plan on releasing at the end of October so please use the workaround until then 🙂

Do you know how to test this nf-azure plugin with nf-schema? @Ben Sherman is there a way I can test this plugin along with nf-schema? I always have issues with local builds + remote plugins sadpanda https://github.com/nextflow-io/nextflow/pull/6428

nf-schema uses the built-in Nextflow version of nf-azure. So you can just compile a local version of Nextflow to test this

So you can just compile a local version of Nextflow to test this

Whenever I do this it shouts at me about not being able to use remote plugins 😕

Okay keep me updated!

@Adam Talbot I would try to write a unit test in your PR that reproduces the issue from nf-schema so that you don't have to test both

Thanks for the clarification, guys!

No AzFileAttributes tests shocked