Re: post-review problem

Sorry about that. Background, this is a customized reviewboard 1.0 upgrade to 1.6.6. Previous installation post-review had in python a VERSION = "0.8" Now I get: >>> RBTools 0.4.1 >>> Home = /var/www >>> HTTP GETting api/ >>> HTTP GETting https://127.0.0.1/reviewboard/api/info/ >>> Using the ne

Re: Final procedure for perforce integration?

Hi Christian, What's the procedure? I will need to let organization I work for know that before going forward. Thanks, -Neel. On Thursday, 12 April 2012 20:33:22 UTC+5:30, Christian Hammond wrote: > > Hi Neel, > > We really need to land a patch for proper ticket-based auth. The problem > is th

Re: Problem with uploading consecutive diffs with updates

Can someone help me out here? On Wed, May 2, 2012 at 1:37 PM, Robert Dailey wrote: > So I'm using Perforce and I upload my initial reviews (as well as follow > up changes and updates) using this command. Note that this is a "Custom > Tool" in P4V: > > %C --server=http://reviewboard.company.com --

unable to create review request from post-review

Hi, I am using post-review 0.4.1 and I am unable to create review request: Following are the detailed logs: Failed to execute command: ['svn', 'info', '.xml'] ['.xml: (Not a versioned resource)\n','\n', 'svn: A problem occurred; see other errors for details\n'] Please help thanks Ashi

Problem creating a review after upgrading to 1.6.6 on CentOS 5.8 (patch file too large?)

I recently upgraded our ReviewBoard server to version 1.6.6. First, thanks for a great product and an easy upgrade; the upgrade instructions worked flawlessly. The issue described below may have nothing to do with the upgrade, but I thought I'd mention it just in case. Today a user complained

Re: Problem creating a review after upgrading to 1.6.6 on CentOS 5.8 (patch file too large?)

Hey Alfred, This is a database configuration issue. I don't know the key off-hand, but you can increase the max packet size in MySQL. That said, we do have a 1MB limit for diffs now (but that's not what you're hitting), as Review Board can get bogged down if too many people are processing large d

Re: Problem creating a review after upgrading to 1.6.6 on CentOS 5.8 (patch file too large?)

On May 7, 2012, at 15:20, Christian Hammond wrote: > That said, we do have a 1MB limit for diffs now (but that's not what you're > hitting), as Review Board can get bogged down if too many people are > processing large diffs at once. It's not configurable yet, but in general, > very large diffs

Re: Problem creating a review after upgrading to 1.6.6 on CentOS 5.8 (patch file too large?)

On Mon, May 7, 2012 at 12:33 PM, Alfred von Campe wrote: > On May 7, 2012, at 15:20, Christian Hammond wrote: > > That said, we do have a 1MB limit for diffs now (but that's not what > you're hitting), as Review Board can get bogged down if too many people are > processing large diffs at once. It'

Re: Problem creating a review after upgrading to 1.6.6 on CentOS 5.8 (patch file too large?)

On May 7, 2012, at 16:56, Christian Hammond wrote: > Memory and how much of it that memcached can use is crucial. We cache a > *lot*, since fetching files from the repository, patching them, and > generating diffs is all very expensive. So the more that memcached can hold > at once, the faster

Re: No supported repository could be accessed at the supplied url.

Find the cause of the problem, in the subversion "svnserve.conf" file, write a wrong realm. Thanks again. On May 6, 9:46 pm, q wrote: > Thanks for your reply. > > The server is centos, and the Review Board repository configuration > like this: > Name: revew > Hosting service: Custon > Repository