Offending exon with "non canonical" (and non existent) boundaries, and an artificial intron about apollo

[childers]

I exported the annotations for this scaffold as gff3 to see what was happening at the feature level. There is a non_canonical_three_prime_splice_site feature located at coordinated that would put it inside a CDS/exon boundary.

It is possible that this happened due to the user adjusting the boundary, creating the non-canonical splice site flag. For some reason the non_canonical_three_prime_splice_site state was not properly reset when the feature was later adjusted.

[nathandunn]

Want to retest this in 2.0.0.

[monicacecilia]

After testing, have not been able to reproduce. This is good!
I am closing this issue for now, and I am positive 2.0 won't be sending this error again - connectivity and latency should not be that much of an issue with the new architecture. here's hoping.