hiya. So sarek v3.7.0 / 3.7.1 at least doesn't seem to work for

-profile test,docker

currently (under nextflow 25.10.2). complaining about inability to get/validate s3 files (similar to issue above https://nfcore.slack.com/archives/CGFUX04HZ/p1765807282249489?thread_ts=1765581426.397549&cid=CGFUX04HZ). I've reverted back to 3.6.0 (git checkout in this case) and test works again. Are any other issues expected for 3.7.1 version outside of test profile given this observation?

I believe this is fixed here: https://github.com/nf-core/sarek/pull/2083

Ok

Jon just removed the validation completely (prob comes back later for someone that wants the validation), but I think this also surfaces some deeper issues with setting defaults that are not accessed when other parameters are set (here the igenomes_ignore one).

Ok, thanks. Perhaps best to stick to earlier version for a bit then?

Grrr, not being able to access public s3 buckets with private credentials is SO frustrating. This should be fixed at the Nextflow end frankly

I guess here it is extra annoying because the igenomes-ignore flag prevents it from being used anyways, but we can't set a conditional check in nf-schema (I think)

Rike, can you and Jon push to get this actually fixed in Nextflow?

There is an ongoing discussion/PRs here: https://github.com/nextflow-io/nextflow/issues/4732

The above was due to nextflow/pipeline defaulting to personal AWS configuration stored in the environment in question