Regarding error message interpretation: This error...
# random
j
Regarding error message interpretation: This error message is hunting me down now for the second time this week. Want to guess what is the actual error that caused the pipeline to crash? (I'll put it in the thread below)
A missing comma in
modules.config
😁
facepalm 3
🫠 1
a
Missing comma, error Extra comma, believe it or not, error
πŸ‘Œ 1
πŸ˜† 2
nod 1
j
I understand that it causes an error, commas are important – But I don't understand why such a misleading error message is triggered πŸ™ƒ
r
it doesn’t even need to be a comma. Can be other syntax errors as well πŸ™ˆ
party dino 1
j
I'll remember that if I ever get confused again
p
It's not that Nextflow deliberately triggers the confusing error message, it's just that it doesn't know where the error comes from
Nextflow is a DSL built on top of Groovy. So when you run the pipeline, your Nextflow DSL code is basically converted into a Groovy script.
The error will come from that groovy script, but it's not helpful to report that exact error as it won't correspond to the code in your editor
So Nextflow / the Groovy AST basically does the best it can. Which is often not very good.
If you want to nerd out on this stuff we had a good discussion about it in this podcast
πŸ’― 1
You'll be pleased to know that error reporting is one of the major projects we're working on in 2024 for Nextflow πŸ™‚
deploy parrot 2
πŸ’₯ 1
🌈 1
j
Thanks Phil! Of course I know (fundamentally) what is behind the error messages and that they are not deliberately misleading. It wasn't meant as a rant, I was just beating my head into the screen when I finally succeeded with debugging this error πŸ˜„
p
We've all been there! πŸ˜…
r
7cqpl4.jpg
πŸ˜† 1
🫠 2