Typed processes are still a preview feature, no?
# team-maintainers
j
Typed processes are still a preview feature, no?
p
For a few more weeks, yes
Should be stable in 26.10Β¨
party this 1
Though they will still be opt-in
j
I think it's on our road map anyway. Might be jumping the gun somewhat, but good to get it done
j
There's a converter built into the language server, right?
j
Yeah, I'm not saying it's rocket science or anything...
I'm sure there'll be wrinkles along the way
j
Problems I forsee: β€’ Would need to bump the minimal Nextflow version β€’ Could require a lot of concomitant changes to subworkflows, e.g. where
[]
is used in place of a null input
This is what we planned a while ago
Several of those dates are slipping now though
Mostly, it looks like it might make most sense to do workflow outputs together with record types
j
[11:52 AM]
Mostly, it looks like it might make most sense to do workflow outputs together with record types
Yes, that's my plan for rnaseq soonish
πŸ‘πŸ» 1
p
My thinking is: try to get as many pipelines up to date as possible (see my hackathon project), then work on module updates (project) and then go to town
j
Records are a whole other kettle of fish, I'm not sure we've even figured out how to use them in an nf-core context, or whether they're desireable? β€’ how do we manage sample metadata in records (keep a meta map/record, or move the fields to the base map? in which case, how do we emit them from the process) β€’ defining best as possible a standard vocabulary for field names to avoid endless renaming. i think this could be really thorny, there is always going to be a conflict between what's useful to name fields in a pipeline vs what's useful to name them in a generic module
It would be comparatively simple to migrate to static typing while maintaining tuples
p
yeah I think static typing is probably the easier of all of these
it's record types + outputs that I want most though πŸ˜†
Once we have outputs, we can start using them for all kinds of cool new things
j
IMO the new output syntax is impractical in rnaseq without records. There will just have to be .... discussions....
p
Better lineage, pipeline chaining, etc. etc.
j
Workflow outputs are /so good/, I agree, I've been using them in my pipelines
p
honestly I don't really mind how we get there, as long as we get outputs πŸ˜…
j
Currently I'm collating sample-level information into an output record/map in each subworkflow and just passing them down
n
Will the next version be out before the hackathon? Otherwise I would be happy to set up a group to start experimenting and writing some guidelines for static processes. Record types could be part of that but those might need more experimenting than we can do in 2 days
s
workflow outputs are great, except for the fact you have to manually pass them between subworkflows/workflows
as Jon says, that really shows in rnaseq
p
Will the next version be out before the hackathon?
Yes, aiming for the week before
πŸ™Œ 1
We refer to the process internally as "Summit driven development" πŸ˜†
🀣 3
n
Okay I'll submit a PR for a project later today πŸ˜‰
Anyone wanna co-lead that one?
j
Can probably count me in! I'll be dragged off to training rooms at times, but I'm obviously keen to work on it
πŸŽ‰ 2
n
Yeah I'll put myself as the main contact point, feel free to drop by as much as you like πŸ˜‰
❀️ 1
m
Typed processes are still a preview feature, no?
---
For a few more weeks, yes
Should be stable in 26.10
With the same syntax ? I remember we got bitten by the last preview feature when it turned stable with a different interface and the reason was that β€œpreview features are not stable, use at your own risk”. I don’t want the same to happen again
100 rainbow 1
p
@Ben Sherman I don't think the syntax is changing, is it?
b
correct, no syntax change this time
for the code migration, see also this: github.com/nextflow-io/agent-skills
j
I completed a working version of the rnaseq migration. Ben has promised to review and may call me silly, but thought it would be good to have something concrete to argue about at the hackathon: github.com/nf-core/rnaseq/pull/1945
πŸ”₯ 1
πŸ‘€ 1