Re: Which recommended Apache MPM to use with Reviewboard + extensions

f Reviewboard has been out recently. We planned to upgrade our Reviewboard application, but i saw you have changed some things, especially the extension functionality. So i need to check if our extensions are always compatible. Regards, Vincent -- Get the Review Board Power Pack at http:/

Re: DJblets _check_expired() issues

I opened another topic: https://groups.google.com/forum/#!topic/reviewboard/kS23n4m5aNw These above issues seem to be caused by the Apache configuration i used (MPM worker instead of MPM fork). Le mardi 10 décembre 2013 17:18:46 UTC+1, Vincent G. a écrit : > > Hi, > > Before to

Which recommended Apache MPM to use with Reviewboard + extensions

* wsgi.multiprocess = True If wsgi.multithread is set to False (by using Apache MPM Fork example), no problem. Best regards, Vincent G. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us

DJblets _check_expired() issues

elf).__init__(*args, **kwargs) URLHook(self, patterns('', (r'^rbmetrics/', include('rbmetrics.urls' TemplateHook(self, "base-scripts-post", "rbmetrics/metrics_init.html", apply_to=['v

DJblets _check_expired() issues

self).__init__(*args, **kwargs) URLHook(self, patterns('',(r'^rbmetrics/', include('rbmetrics.urls'TemplateHook(self, "base-scripts-post", "rbmetrics/metrics_init.html", apply_to=['v

Re: Error uploading diff

Hi Chris, It turns out the repository credentials that review board was using was a former employees whose account was deleted. Thanks for your help. Thomas On Wed, May 11, 2011 at 3:39 PM, Thomas Vincent wrote: > Hi Chris, > I posted the logs at http://pastebin.com/aB4a8iMr . I see the

Re: Error uploading diff

ur PySVN install, too. > > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > > On Wed, May 11, 2011 at 3:23 PM, Thomas Vincent wrote: > >> Hi, >> I upgr

Re: Error uploading diff

: 'One or more fields had errors', 'code': 105}} Error uploading diff The generated diff file was empty. This usually means no files were modified in this change. Try running with --output-diff and --debug for more information. Your review request still exists, but the dif

Re: Error uploading diff

gt; > It looks like there are two things going wrong. The first is that Review > Board's having some sort of trouble fetching server information from your > repository. The second is that locally, it's been unable to generate a diff. > > So assuming Subversion, what happens

Re: Error uploading diff

n "svn diff" on your > checkout? > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > > On Tue, May 10, 2011 at 5:49 PM, Thomas Vincent wrote: > >> Hi, &g

Error uploading diff

Hi, I am getting the following errors when I try to upload a file using post-review. >>> Got API Error 210 (HTTP code 200): There was an error fetching extended >>> information for this repository. >>> Error data: {'deprecated': {'in_version': '1.5'}, 'stat': 'fail', 'err': >>> {'msg': 'There was

RE: Realized web-based post-commit reviews

Good work! How about CVS? From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On Behalf Of Martin Sent: Thursday, April 07, 2011 11:53 AM To: reviewboard@googlegroups.com Subject: Re: Realized web-based post-commit reviews Congratulations, I

RE: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors

That's the trick... in /usr/bin/ Thx Vincent -Original Message- From: chip...@gmail.com [mailto:chip...@gmail.com] On Behalf Of Christian Hammond Sent: Wednesday, March 30, 2011 9:51 PM To: Vincent Yee Cc: Christian Hammond; reviewboard@googlegroups.com Subject: Re: post-review

RE: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors

rror path, It returns the original error: >>> Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to server >>> failed; check $P4PORT.\nTCP connect to :1666 failed.\nconnect: :1666: >>> Connection refused\n']}, u'stat'

RE: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors

es', u'code': 206}, u'deprecated': {u'in_version': u'1.5'}} There was an error creating this review request. The repository path "repoman.example.com:1666" is not in the list of known repositories on the server. Ask the administrator to add thi

RE: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors

Of Christian Hammond Sent: Wednesday, March 30, 2011 3:41 PM To: reviewboard@googlegroups.com Cc: Vincent Yee Subject: Re: post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors Sounds like the Review Board server isn't able to contact your Perforce server for

RE: 500 - Internal Server Error | Review Board

Thanks... That fix the problem now I am able to see the login and registration GUI etc... Vincent From: chip...@gmail.com [mailto:chip...@gmail.com] On Behalf Of Christian Hammond Sent: Thursday, March 24, 2011 5:28 PM To: reviewboard@googlegroups.com Cc

Re: Aggregated diffs and added files

Hi.actually I have the same problem.but maybe it is because I have am still using the beta version Sent using a Sony Ericsson mobile phone Original message From: Christian Hammond Sent: To: reviewboard@googlegroups.com Subject: Re: Aggregated diffs and added files Without seeing th

Question about the API info

Hi I am not sure that if this is a doc bug or not: http://www.reviewboard.org/docs/manual/dev/webapi/reference/apicalls/login/#api-login As you said the type of password is Boolean, which is confusing me, could you please check it? BR/Vincent -- Want to help the Review Board project? Donate