diff options
| author | BonfaceKilz | 2022-05-05 11:25:07 +0300 |
|---|---|---|
| committer | BonfaceKilz | 2022-05-05 11:25:07 +0300 |
| commit | fce8ae5156c852fd448fc3909c0dddd47332d6bc (patch) | |
| tree | 1cfafc8e783afd24a48ec05263c335e66db7d8f8 | |
| parent | d336b867ccad612d35cb6ceafaa545ae1577e845 (diff) | |
| download | gn-gemtext-fce8ae5156c852fd448fc3909c0dddd47332d6bc.tar.gz | |
Track new issue on batch submitting unknown strains
| -rw-r--r-- | issues/uninformative-error-when-batch-submitting-unknown-strains.gmi | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/issues/uninformative-error-when-batch-submitting-unknown-strains.gmi b/issues/uninformative-error-when-batch-submitting-unknown-strains.gmi new file mode 100644 index 0000000..bb0a4e5 --- /dev/null +++ b/issues/uninformative-error-when-batch-submitting-unknown-strains.gmi @@ -0,0 +1,13 @@ +# Uninformative error when batch submitting unknown strains + +# Tags + +* assigned: bonfacem,zachs +* keywords: metatadata +* status: unclear +* priority: medium + +## Description + +When batch submitting temporary traits, the upload will sometimes fail with the error `The format of the file is incorrect, or it contains unknown strains.` In my case, it is because I have data for strains that don't yet have GN genotypes (BXD224, BXD226). It would be pretty helpful when working out which strains to drop (or spell correctly) to have the offending strings reported. Is this possible? + |