cache warning

Hi, I'm using the latest version of reviewboard and it should have the large data caching feature. But I keep getting this warning in the log WARNING - Failed to fetch large data from cache for key review.datadomain.com:diff-sidebyside-hl-359: Error -5 while decompressing data. Viewing large di

Re: cache warning

I see Djblets-0.4.dev_20081201-py2.4.egg under lib directory. Tam On Dec 11, 1:40 pm, "David Trowbridge" wrote: > Are you up to date with djblets too? > > -David > > On Thu, Dec 11, 2008 at 11:01 AM, TP wrote: > > > Hi, > > > I'm using the

Re: Diff error

You need to use post-review script. RB expects different headers in diff output. On Feb 12, 10:55 am, Dave wrote: > I've setup reviewboard 1.0 alpha 2 release on CentOS 5.2. I've used > p4diff to generate the diff and when I tried to upload the diff file, > I am getting the following error mess

Re: Feature request

I have a Perforce commit trigger to update the status to submit as well as updating the pending changelist number with the actual submitting changelist. On Mar 2, 1:57 pm, plumpy wrote: > There is a post-commit hook for subversion that will automatically > close reviews. That's not at all what y

child pid exit signal Segmentation fault (11)

Hi, I notice few of these in the apache log. Users also reported bad http status. [notice] child pid 28735 exit signal Segmentation fault (11) I'm running httpd-2.2.3-11.el5_1.3, mod_python-3.2.8-3.1, P4Python/ LINUX26X86_64/2008.1/161104. How can I find out what is crashing apache? Much th

Re: child pid exit signal Segmentation fault (11)

I disabled PyLucene but still seeing the problem. The Apache core files aren't very useful. I switched to lighttpd-1.4.22-2.el5.rf and got backend crashes as well. Is there any problem with python-2.4.3-24.el5? -TP On May 12, 10:36 pm, Christian Hammond wrote: > Hard to say.

Re: child pid exit signal Segmentation fault (11)

Btw I'm running RB 1.0alpha2 in RHEL 5.2 x64 VM. The VM has 4 vCPU and 8GB of RAM. The local memcache is set to 2GB max. On May 15, 12:06 pm, TP wrote: > I disabled PyLucene but still seeing the problem. The Apache core > files aren't very useful. > > I switched to lightt

post review for a specific mercurial changeset

Hi, We're using hg postreview extension with RB. How do we submit a review for a specific changeset if we've multiple outgoing changesets? For example, if we have local changesets 1, 2, 3 and I want to submit a review for 2. Running "hg postreview 2" would include all three changesets. Thanks!

Re: Failed upgrade from 1.6.4.1 to 1.6.8 (evolution failed)

Got the same issue with 1.6.7.1 to 1.6.9 # rb-site upgrade /var/www/site Rebuilding directory structure Updating database. This may take a while. Creating tables ... Upgrading Review Board from 1.6.7.1 to 1.6.9 Project signature has changed - an evolution is required Installing custom SQL ... Inst

Re: Failed upgrade from 1.6.4.1 to 1.6.8 (evolution failed)

This fixed it. Thanks! On Jun 19, 3:41 am, Christian Hammond wrote: > In the meantime, good news! There is a fix. If you can reach the Django > admin UI, go into the Database -> Django Evolutions -> Versions area and > delete the "Hinted version" you have there. Then repeat the rb-site > upgrade