Closed scharch closed 6 years ago
arg, thanks.
This is ringing a bell, I think it happened once before? But then I'm not sure why it can still happen, since I would've fixed it. The deal is it usually gets the codon position for the new allele from its template gene, but for homozygous novel alleles the template gene gets removed, so I should be storing the codon position directly in the new allele's info before removing. But it apparently doesn't happen every time we remove the template, since, well, it works fine most of the time.
In any case, I think this should fix it -- I don't have an easy way to test it, since it's an uncommon situation, but if it's easy for you to switch to dev for a moment and see that'd be great.
oh, I remember. It happens only when there's two novel alleles from the same template gene, and the first of those thinks that the template should be removed, then it crashes when it tries to handle the second one since the template is gone. That ^ commit should indeed fix that.
Yep, that worked, thanks.