if only we had a `machine god` to fix the failing ...
# infrastructure
e
if only we had a
machine god
to fix the failing pipelines on AWS :D
m
we have @Rike Hanssen
e
or
machine goddess
party this 1
r
watcha need?
I see other pipelines failing for the same reasons or maybe other reasons now that I look closer
r
what nextflow version do you run this locally with ? (I take it it passes there)
👌 1
e
26.04.6
r
the robot found the cause:
Copy code
What happened
The run failed at compile time (before any task ran), so progress shows 0 processes. The fatal line:

Missing process or function paramsSummaryLog(...)
 -- Check script '.../subworkflows/nf-core/utils_nfschema_plugin/main.nf' at line: 5

That subworkflow does include { paramsSummaryLog } from 'plugin/nf-schema'.

Now the mechanism, from the log and the source at the exact commit (0bad731) that ran:

The pipeline's own nextflow.config pins nf-schema@2.7.2, which does export paramsSummaryLog.
But the run log says: Downloading plugin nf-schema@3.0.0. So the unpinned latest (3.0.0) was loaded instead, and paramsSummaryLog was removed/changed in nf-schema 3.0.0 → "Missing process or function".
Why the pin was ignored
Look at the extra config attached to this launch (the Slack-notification block):

plugins {
  id 'nf-slack@0.5.0'
}

This plugins {} block in the launch/workspace config overrode the pipeline's plugins { id 'nf-schema@2.7.2' } block. Result: nf-schema lost its version pin and Nextflow resolved it to the latest release, 3.0.0, which is incompatible with this pipeline revision.

The fix
Add the pipeline's nf-schema pin back into the custom plugins block so both plugins are declared with versions:

plugins {
  id 'nf-slack@0.5.0'
  id 'nf-schema@2.7.2'
}

Keep the rest of the Slack config as-is. Relaunch with that change and the compile error will go away. (Longer term, the Slack plugins{} snippet lives in the workspace/launch config used across nf-core test runs — anywhere it's injected it needs to carry the matching nf-schema pin, or it will silently un-pin nf-schema for every pipeline it touches.)
so it looks like that this was not an issue until recently, because latest plugin was 2.7.2 but with the new release this is now an issue. I hadn't considered that plugin scopes are not additive but overwriting. will add it my list of thigs to do
cloud.seqera.io/orgs/…/… this one is starting up now
m
Nice catch
r
also way to nerd snipe me. I had just said to someone, that I really need to focus today 😆
🤣 2
p
You called? 😆
🤣 1
r
I might update the CEs for the time being, so not everything starts failing, until pipelines have this merged in. aaahahhhh why are there so many hidden dependencies
m
n
Yeah it's been bugging us for quite a long time, this was bound to go wrong at some point 😕)
r
Your run succeeded @Evangelos Karatzas
🙌 1
e
Oh nice, my most productive yerba mate 10 minute break. Thanks!
Shall I delete the failing ones? Maybe keep one for the bug reference?
r
no it's fine to keep them
m
Please send a prayer to our machine goddess
❤️ 1
🙏 1
As the first priest, I collect donations
🪙 1
r
600 up front
party this 1
💯 1