A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

I believe I"ve found root cause. It looks like NF's internal parser for YAML params and JSON params will wind up with different Java types at times and thus not hash. e.g. `0.4` provided via YAML winds up as `Double(0.4` and JSON gets `BigDecimal(0.4` so if you supply YAML params, and I already suspected Tower's `resume` uses JSON, there you go

What version of Nextflow? I guess older, I think this is one of the many small things that we tried to clean up with the new config parser

<@U032S9298G6> said it was fixed in Edge, provided one is using a newer style params block.

I’m kind of surprised this is such an obscure error given the potentially large blast radius in terms of total usage, but I suspect at the end of the day people tend to chalk up resume failures as not being worth the hassle to track these things down

<https://github.com/nextflow-io/nextflow/issues/7776#event-32728410933|github.com/nextflow-io/nextflow/issues/7776#…>

Even here, where there were a bunch of workflows potentially affected by this (submitted originally as YAML to Tower), running at high volume, it took a few years to get spotted, and even then it was a “hey, someone should look into this” situation. So :shrug: