Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pipeline error when no --mito_name param is provided #286

Closed
JoseEspinosa opened this issue Jun 1, 2023 · 1 comment
Closed

Pipeline error when no --mito_name param is provided #286

JoseEspinosa opened this issue Jun 1, 2023 · 1 comment
Labels
bug Something isn't working
Milestone
2.1

Comments

@JoseEspinosa
Copy link
Member

Description of the bug

When no --mito_name parameter is provided to the pipeline the following error is raised:

ERROR ~ A process input channel evaluates to null -- Invalid declaration val mito_name

Command used and terminal output

No response

Relevant files

No response

System information

No response
@JoseEspinosa JoseEspinosa added the bug Something isn't working label Jun 1, 2023
@JoseEspinosa JoseEspinosa added this to the 2.1 milestone Jun 1, 2023
bjlang pushed a commit to bjlang/nf-core-atacseq that referenced this issue Jun 2, 2023
Fix nf-core#277 and nf-core#286
4deaa05
@JoseEspinosa JoseEspinosa mentioned this issue Jun 6, 2023
Merged
9 tasks
@JoseEspinosa JoseEspinosa reopened this Jun 9, 2023
@JoseEspinosa
Copy link
Member Author

Fixed in #287

@JoseEspinosa JoseEspinosa mentioned this issue Jul 14, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
2.1
Development

No branches or pull requests
1 participant
@JoseEspinosa