Replies: 6 comments 4 replies
-
|
Beta Was this translation helpful? Give feedback.
-
Hi @kevyin , This is an interesting point - I'm not sure if this is a bug/feature request. In any case, it could be resolved at design level since all of these params could essentially be wrapped into a tuple and then passed into the process. And within the prcess you can use something as shown below
... to essentially use all of these together. |
Beta Was this translation helpful? Give feedback.
-
Hi @abhi18av , It's not just inputs, in the example, but all kinds of Channels that goes into the 255 maximum.
255 seems like some integer limit, 2^8 = 256 |
Beta Was this translation helpful? Give feedback.
-
I don't see how this can happen with the example provided?
|
Beta Was this translation helpful? Give feedback.
-
@pditommaso Here it is again attached and the log |
Beta Was this translation helpful? Give feedback.
-
Hi @pditommaso @abhi18av The actual error message says "arguments" I've renamed the issue |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Bug report
Expected behavior and actual behavior
In DSL2 there is a limit to the number of channels/references to channels in a *.nf script
Expected behavior is that there is no such limit
Steps to reproduce the problem
I've attached a toy example in the comment below
#2411 (comment)
Also attached: https://github.com/nextflow-io/nextflow/files/7426077/mytest.nf.zip
Program output
Environment
Nextflow version: 21.04.3
Java version: openjdk version "1.8.0_292"
OpenJDK Runtime Environment (build 1.8.0_292-8u292-b10-0ubuntu1~20.04-b10)
OpenJDK 64-Bit Server VM (build 25.292-b10, mixed mode)
Operating system: Linux
Bash version: GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
Additional context
nextflow.log
(Add any other context about the problem here)
Beta Was this translation helpful? Give feedback.
All reactions