I just read this again more carefully:
> Actually, the reason you're having this problem is that your release is
so old. If you upgrade, this shouldn't happen on newer review requests.
That sounds like even on the new server this particular review will be
broken, but new reviews should not end up in this state. Is that right?
On Wednesday, January 16, 2013 10:55:34 AM UTC-8, Steve wrote:
> I get about 1 of these per month, but I have 2 this week and it's getting
> to be a real problem. Developers paste large amounts of text into the
> Testing Done field, after which going to the main page for the review
> yields this:
> Something broke! (Error 500)
> It appears something broke when you tried to go to here. This is
> either a bug in Review Board or a server configuration error. Please
> report this to your administrator.
> The odd thing is we can go around the main page to the diff page and see
> the text in Testing Done, which is baffling. In other words,
> fails with the above error, but
> looks fine. This is really causing problems for our developers. I have 3
> questions in descending order of importance:
> 1. How can I repair a review when it gets in this state?
> 2. What guidelines can I give my developers to prevent this from happening?
> 3. Why does the main page fail, when the text appears to be fine in the
> diff_header page?
> We're using 1.5.5 on CentOS 5.
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at