Attn: Jelmer & David (was [Fwd: [Rails-core] Re: ERROR on Rails Subversion repository])

[Hendy Irawan]

Dear Bazaaristas,

Attn: Jelmer Vernooij, David Allouche

Continuing our recent discussion in IRC and Launchpad Questions, this is 
one reply I got from Rails-core.

Although I'm not sure about the exact culprit, there is possibility that 
this happens not only on Rails SVN server, but also a bunch of other SVN 
servers in the world. Be it misconfigured, having an old version of 
library, or something.

 From the description, and from experiments, it seems true that limiting 
does have the "nice" effect of avoiding these errors, which means that 
can probably do a workaround.

My proposal is that bzr-svn will issue "svn log -v" in bulk batches, 
i.e. 1000 revisions at once. If it can work out, then it should work 
more reliably with "buggy" SVN servers. And the running performance 
shouldn't be that bad. Considering that even in a 10,000 revisions 
repository, we'll only do that 10 times. And that is still better than 
try to do that once, and fail. :-(

I'll also try joining the Subversion list to see if anyone comes up with 
a better solution. But even if Subversion will have  a fix in the 
future, there's no guarantee that everyone in the world will be rushing 
to update it... So a workaround is still needed unfortunately. :-(

As for Ruby on Rails, it is a fast evolving project now... But not 
everyone is a committer, and not every patch is accepted (that's the 
state of most open source projects nowadays anyway). Having Rails in 
Launchpad will make it easy for everybody to contribute a patch (or try 
to contribute a patch), and/or test new ideas without affecting the main 
SVN repo the original developers have.

And if enough people use Launchpad servers, I think it'll reduce, not 
increase, the load on Ruby on Rails SVN servers. Which is probably a 
good thing for them. :)

Hopefully we can sort this out gradually. Thank you.


-------- Original Message --------
Subject: 	[Rails-core] Re: ERROR on Rails Subversion repository
Date: 	Wed, 19 Sep 2007 01:34:00 +0200
From: 	Mislav Marohnic' <mislav.marohnic at gmail.com>
Reply-To: 	rubyonrails-core at googlegroups.com
To: 	rubyonrails-core at googlegroups.com
References: 	<46F04ACB.3010108 at gmail.com>



On 9/19/07, *Hendy Irawan* <gauldong at gmail.com 
<mailto:gauldong at gmail.com>> wrote:


    ceefour> svn log -v http://svn.rubyonrails.org/rails/trunk
    svn: REPORT request failed on '/rails/!svn/bc/7513/trunk'
    svn: REPORT of '/rails/!svn/bc/7513/trunk': Response exceeded maximum
    number of header fields. (http://svn.rubyonrails.org)


Umm ... try it with "--limit N". Otherwise you'll be requesting the 
whole svn log of Rails trunk, verbosely. I don't know how the Apache 
svn_dav module uses HTTP headers, but with such huge data you're bound 
to have "something exceeded maximum something" errors.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google 
Groups "Ruby on Rails: Core" group.
To post to this group, send email to rubyonrails-core at googlegroups.com
To unsubscribe from this group, send email to 
rubyonrails-core-unsubscribe at googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---


-- 
Hendy Irawan
www.hendyirawan.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20070919/4f922387/attachment.htm