Nick Hengeveld wrote on Thu, Feb 09, 2012 at 17:29:14 -0800: > On Wed, Feb 8, 2012 at 12:59 PM, Greg Stein <gst...@gmail.com> wrote: > > So... this isn't really so much about "svn must allow for HTTP/1.0" > > (yes, we'll work on it), but that github could also provide better > > service overall by updating its proxy. > > > > I've been looking into what it would take to update our proxy. I have an > nginx > configuration in my dev environment that handles requests with chunked > transfer-encoding and we could feasibly deploy something like this to > production. However, I'm now getting a different error on the client: > > svn: E235000: In file 'subversion/libsvn_ra_serf/update.c' line > 1769: internal malfunction > Aborted >
As it happens I found and fixed this particular issue a few hours ago; the fix is nominated for backport towards 1.7.3. > From what I can see at > https://github.com/apache/subversion/blob/trunk/subversion/libsvn_ra_serf/update.c#L1698-1771 > it looks like the client is trying to process an add/open file. The > checkout > I'm testing is small and contains only one file, and this is what the > server is returning for that file: > > <S:add-file name="README.txt" > > <D:checked-in><D:href>/github/sample/!svn/ver/3/trunk/README.txt</D:href></D:checked-in> > <S:set-prop name="svn:entry:committed-rev">3</S:set-prop> > <S:set-prop > name="svn:entry:uuid">faa06a63-5b49-ecd5-b7fc-ce57b7db7bff</S:set-prop> > <S:set-prop > name="svn:entry:committed-date">2012-02-09T22:12:11.000000Z</S:set-prop> > <S:set-prop name="svn:entry:last-author">subversion.user</S:set-prop> > <S:txdelta> As you probably know from the part of libsvn_ra_serf you cited, the <S:txdelta/> tag is the one that causes the blow-up. A quick grep through the libsvn_ra_serf and mod_dav_svn sources leads me to conjecture that ra_serf requests a "send-all"=false REPORT, but receives from your server a "send-all"=true response. > U1ZO > AQAAMQs4AnicazAEAAEzALIxeJwLycgsVgCixDyFotTElNxUHYXSgpTEktQUhbLMRIVEBUM9c4XknMzUvBI9rsh8PS4AnrgP > sw== > </S:txdelta> > <S:prop><V:md5-checksum>5fa5200f0f095d120c13870e107dfb7a</V:md5-checksum></S:prop> > </S:add-file> > > I'm using a Linux client installed > from CollabNetSubversion-client-1.7.2-1.x86_64.rpm. > svn --version reports: svn, version 1.7.2 (r1207936) > > What's the best way to track down issues like this? I'm not currently > familiar > with svn client debugging but would be happy to learn. > For svn client debugging, the first thing to do is to build --enable-maintainer-mode; this enables stricter compiler warnings and internal debugging checks (guarded by '#ifdef SVN_DEBUG'). > -- > For a successful technology, reality must take precedence over public > relations, for nature cannot be fooled.
