-
Notifications
You must be signed in to change notification settings - Fork 412
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
Avoid misleading error messages concerning sample-sheets #1629
Comments
I faced a similar issue. But the error message is misleading and lead me to double and tripple check my sample sheets |
Thanks for reporting that, @dansteiert |
I am getting the same error: The sample-sheet only contains tumor-samples, but the following tools, which were requested by the option "tools", expect at least one normal-sample : ascat Any possible solution? |
Is there another error message besides the one related to the sample-sheet? The error message might not be printed to |
No error message. My job terminates with the followingWARN: The default Panel-of-Normals provided by GATK is used for Mutect2. -- Check script '/home/sarek/.nextflow/assets/nf-core/sarek/main.nf' at line: 342 or see '/mnt/f/ARIA/sarek_output/log/M14TIL121.log' file for more details |
Which version of Nextflow are you using? 24.07.0-edge or later? If so, you can try to revert to
If your running local code, then you can perhaps also try the fix mentioned here. |
I was using nextflow 24.10.0 but now running again with NXF_VER=24.04.4 nextflow run … and seems working... Thank you.. Plus 81 more processes waiting for tasks… |
Description of the bug
This bug has been around for a while now. When Sarek encounters an error is will often issue the correct error message along with a couple of wrong error messages. The wrong error messages are related to the sample-sheets.
Here is an example where Sarek v3.4.3 was given an incorrect path to the VEP-cache, and Sarek gave the following error msg:
The error messages concerning the sample-sheet are wrong and shouldn't be issued in this scenario. (The error message concerning the VEP-cache is fine.)
The error isn't caused by
nf-validation
, but by code in Sarek:sarek/subworkflows/local/samplesheet_to_channel/main.nf
Line 162 in e92242e
sarek/subworkflows/local/annotation_cache_initialisation/main.nf
Line 50 in e92242e
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: