A developer attempted to merge a change with an *extremely* long subject line (in fact, because there was no blank line between the subject and the change detail paragraph, the entire paragraph was the subject line)... and, as a result, it looks like the change violated the database constraint on the length of the subject line, and that and subsequent changes got stuck in SUBMITTED state.
It seems easy enough to reproduce (write a subject >255 characters), and easy enough to clean up, but should it even be acceptable to attempt merging changes in this case?
Affected Version: 2.4.2, but master/2.6-rc* is most likely affected as well.
What steps will reproduce the problem?
1. Create commit with extremely long subject line (>255 chars)
2. Push change to Gerrit review
3. Submit change.
What is the expected output? What do you see instead?
Change should merge or be rejected by Gerrit, but instead gets stuck in SUBMITTED status.
I would think that adding an extra check to com.google.gerrit.server.change.Submit would be sufficient, but the fact that other areas could cause similar problems while inserting to the DB makes me wonder. Also, gwtorm doesn't seem to have any insight into the DB schema after creation, so it's not possible to easily tell if this will violate schema creates before attempting the merge.