Classification grid error message incorrectly states that variants are not resolved
- Dominant language
- Python
- Stars
- 30
- Forks
- 3
- Avg merge
- 9h 28m
- Merged PRs (30d)
- 42
Description
g.HGVS variants (with NC_xxxxx.xx transcripts) were uploaded to Shariant, where these variants/transcripts weren't supported. (All variants raised following error: #6215 ValueError: Couldn't determine annotation consortium for "NC_000001.10"Couldn't determine annotation consortium for "NC_000001.10").
Some variants have an error message in classification grid saying "not resolved showing imported" along with a "Variant matching requires confirmation from administrator". See screenshot:

This error message is incorrect as these variants were successfully resolved, the issue arises later at the step the Shariant tries to regenerate the c.HGVS.
See following for example of error: https://test.shariant.org.au/variantopedia/view_allele/57471.
Other variants show same "not resolved showing imported" along with "variant liftover in-progress", however these are not expected to pass liftover due to their size and type not being supported by clingen allele registry liftover.
See following for example of failed liftover: https://test.shariant.org.au/variantopedia/view_allele/57460
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.