VAGUE ERROR MESSAGES THAT DON'T RELATE TO THE REAL...
# rants
j
VAGUE ERROR MESSAGES THAT DON'T RELATE TO THE REAL PROBLEM shakefistshakefistshakefist
Copy code
ERROR ~ No such variable: task
🤣 2
shakefist 3
m
nextflow or python?
j
Nextflow
I made changes to a local module
I love to feed my Nextflow woes into an LLM (Seqera AI) and get back absolute garbage, also:
Copy code
This line has multiple problems:

    eval() is not a valid Nextflow output qualifier - there's no eval() function in Nextflow output definitions
    topic: is not a standard output qualifier in this context
😁 1
ai thumbsdown 2
🤣 1
m
think of it as your moat winking cowboy
n
Your error usually means that something is wrong with the process code, causing your task to not be properly set 😛 The VScode plugin can help you a lot 😉
j
Yeah, that's what I'm digging for...
nextflow lint
passes with no warnings, annoyingly
...
...
...
I was passing in the wrong tuple to the process
😁 1
MAKING AN ABSOLUTELY HUGE REFACTOR IN A PIPELINE AND MISSING STUFF shakefistshakefistshakefistshakefistshakefist
p
This is what typed records are for feels good
j
🙏🙏🙏🙏🙏 I cannot wait to fully migrate to typing
p
Sneak peek of a screenshot I was doing yesterday for the release blog post this week
m
nice! (could we get syntax highlighing in the error message (something typescript is also really bad at), pretty please?)
p
Can ask. I'm not entirely sure how that'd work 🤔
i
Also waiting impatiently for records, it's too easy to lose track of channel shapes with the current setup
p
@mashehu that plugin kinda confirms all my fears lolsob
m
yep, I was afraid this is one of the weirdly hard problems