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.

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

Pipeline fails quietly when input fastqs are not found #401

Open
SuhasSrinivasan opened this issue Jan 11, 2025 · 0 comments
Open

Pipeline fails quietly when input fastqs are not found #401

SuhasSrinivasan opened this issue Jan 11, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@SuhasSrinivasan
Copy link

SuhasSrinivasan commented Jan 11, 2025

Description of the bug

When input fastq files in the sample sheet are not found, the pipeline does not display this error in the console/terminal.
The other initial steps like genome indexing still continue, but the fastq error can only be found in the log file.

It will be helpful if the error is shown in the console so that the user can quickly resolve the issue.

Command used and terminal output

Relevant files

No response

System information

This seems as a better order to list the system information, from lowest to highest level.

Version of nf-core/atacseq: 2.1.2
Nextflow version: v24.10.3
Container engine: Docker 27.4.1
OS: Ubuntu 22.04.5 LTS x86_64
Executor: Local
Hardware: Desktop

@SuhasSrinivasan SuhasSrinivasan added the bug Something isn't working label Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant