Re: RevewBoard 1.5.2 + RBTools-0.3.2-py2.6 + Perforce + Pre-commit Review - '500 Error' when CLN changed after p4 submit

2011-07-05 Thread Polo Wang
Hi Christian, Thank you for helping. Here are the reproduce procedures of the error we encountered: 1. Run post-review on a chagnelist (e.g. chagnelist = 703920), Review Request URL = http://mydonain.com/reviews/r/100 2. Review the code on ReviewBoard porta

Re: RevewBoard 1.5.2 + RBTools-0.3.2-py2.6 + Perforce + Pre-commit Review - '500 Error' when CLN changed after p4 submit

2011-06-27 Thread Christian Hammond
Hi, So I'm trying to figure out your scenario a bit more clearly. Maybe some background on how we use change numbers will help answer your question. The change number listed on a review request is there for your information only, for the most part. The only time we make use of it is during creati

Re: RevewBoard 1.5.2 + RBTools-0.3.2-py2.6 + Perforce + Pre-commit Review - '500 Error' when CLN changed after p4 submit

2011-06-26 Thread fogy
Hi folks, Is there any setting in ReviewBoard to 'treat WARNING as ERROR'? I'd like to try to turn it off if there is a such setting because the server log was indeed 'WARNING' instead of 'ERROR' so i guess RB can tolerate P4 changelist alteration? Thanks, -fogy- On 6月21日, 下午8時15分, fogy wrote:

RevewBoard 1.5.2 + RBTools-0.3.2-py2.6 + Perforce + Pre-commit Review - '500 Error' when CLN changed after p4 submit

2011-06-21 Thread fogy
Hi everyone, We have RevewBoard 1.5.2 working with Perforce. On client side we use RBTools-0.3.2-py2.6 to do pre-commit review. We can post review request and all comments/updates on RB portal works just fineuntil the changelist was submitted to P4. The problem is that when we submit the chan