... and it's back. keeping open for investigation.

AFAICT, it's been there since Build Annotator was conceived since the 500's are the result of some UI options not fitting within the database column widths. Surely this was reported before February and this is a dupe?

Re #3: I think this bug was about intermittent 500s. What consistent 500s are you talking about?

Anytime anyone chooses: "Tree conflict" or "Bad binary" the server throws a 500 for DB varchar constraint violation. 100% reproducible. Unless we did a schema migration at some point, that should have been the case since those options were added.

ohkay... that's mea culpa then.
That just means we've never used those fields :/

 Issue 791204  has been merged into this issue.