troubles with svn-post-commit hook

2009-11-23 Thread passatijy
Good day everybody. I'm still trying to authomate posting reviews and put my hands on post- commit hook from ReviewBoard-1.1alpha1/contrib/tools/ And when I try to execute the script I'm getting error: [server:~]:1040$ /usr/bin/python /home/username/myrepo/hooks/svn-hook- postcommit-review

fields_changed in changedescs_changedescription

2009-11-23 Thread Ronak
Hi, I get a trackback that looks something like this Traceback (most recent call last): File /usr/local/lib/python2.5/site-packages/Django-1.0.2_final- py2.5.egg/django/core/handlers/base.py, line 86, in get_response response = callback(request, *callback_args, **callback_kwargs) File

Re: troubles with svn-post-commit hook

2009-11-23 Thread passatijy
I fixed it. It was wrong POSTREIVEW_PATH . On 23 ноя, 11:38, passatijy l...@mail.ru wrote: Good day everybody. I'm still trying to authomate posting reviews and put my hands on post- commit hook from ReviewBoard-1.1alpha1/contrib/tools/ And when I try to execute the script I'm getting error:

Re: fields_changed in changedescs_changedescription

2009-11-23 Thread Chris Clark
Out of curiosity what size limit is this likely to be? 80 chars, 1024, 1Mb, 1Gb... :-) Chris Christian Hammond wrote: Hi Ronak, We will be limiting the lengths of these fields in a future version. We're aware of the problem and have encountered this with some users too. Expect a field

Re: fields_changed in changedescs_changedescription

2009-11-23 Thread Chris Clark
Christian Hammond wrote: I don't know off-hand what we're going to set it to. We're thinking about it, and suggestions are welcome. Here's where it gets tricky... We're running up to maximum field lengths for the change info, and that's a combination of multiple fields, including

Re: fields_changed in changedescs_changedescription

2009-11-23 Thread Christian Hammond
We've done a little bit of testing with the server at VMware. There seems to be a mix. We've had people try to dump ~1MB log files in for Description and for Testing Done. Our Review Board admins there are beating people over the head now to stop doing that, but given that we're seeing even that

Re: fields_changed in changedescs_changedescription

2009-11-23 Thread Christian Hammond
Thanks for the information on your server. I agree that 1MB seems excessive, but it does make sense given the results of test cases or tools that people may want to show. Attachment support should help here. That is planned for 1.2. I'd see about 1.1, but I really want to get this release out

RE: fields_changed in changedescs_changedescription

2009-11-23 Thread Paul Scott
I'm pretty sure the current max size for the change info (not the individual fields, but the aggregate) is 65k. -- Paul From: Chris Clark [chris.cl...@ingres.com] Sent: Monday, November 23, 2009 4:44 PM To: reviewboard@googlegroups.com Subject: Re: