Unexpected behavior for --validation-type-to-exclude argument in ValidateVariants. #4642
Assignees
Labels
Comments
|
@droazen @ldgauthier not sure who owns the VariantEvaluation tools, but perhaps one of you can delegate? |
ldgauthier
added a commit
that referenced
this issue
Aug 2, 2019
ldgauthier
added a commit
that referenced
this issue
Aug 5, 2019
samuelklee
pushed a commit
that referenced
this issue
Oct 30, 2019
* Add a test as supposedly described in #4642 * Fix and improve error message * Comment explaining test * finals
|
Not able to reproduce, but assumed closed by #6076. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reposting from the Slack channel:
When I run ValidateVariants on an invalid VCF without providing a reference or any "--validation-type-to-exclude" arguments, I don't get any validation errors. However, if I add "--validation-type-to-exclude REF", then I get validation errors as expected.
Even when I get validation errors in the second case, the error message seems to terminate abruptly:
A USER ERROR has occurred: Input output.vcf fails strict validation: the Allele Count (AC) tag is incorrect for the record at position 1:1262288, 2 vs. 1 of type:The text was updated successfully, but these errors were encountered: