On 22-Jun-05, at 1:30 PM, Ben Collins-Sussman wrote:
> On Jun 22, 2005, at 2:00 PM, Bryan Dyck wrote:
>> svn: Invalid diff stream: [tgt] insn 1 starts beyond the target
>> view position
>> svn: Unexpected end of svndiff input
>> svn: REPORT request failed on '/svn/prima-survey/!svn/vcc/default'
>> svn: REPORT of '/svn/prima-survey/!svn/vcc/default': Chunk
>> delimiter was invalid
>> svn: Checksum mismatch for 'prima-survey/lib/log4j-1.2.9.jar';
>> expected: 'c2ced5f8505fe9d1cae685201e9cba07', actual:
>> [error] [client 192.168.1.1] Provider encountered an error while
>> streaming a REPORT response. [500, #0]
>> [error] [client 192.168.1.1] A failure occurred while driving the
>> update report editor [500, #190004]
> This might be the famous bug in APR that only revealed itself on
> Tiger recently, something to do with APR using poll instead of
> select, or vice versa. The symptom was apache essentially unable
> to stream >64k files to the client.
> The bug has been fixed in the latest HEAD of apr and apr-util.
> As an experiment, you might want to checkout the latest apr/apr-
> util/httpd, and build them all from source and install. Then
> rebuild Subversion, since apr 1.X is binary-incompatible at runtime
> with apr-0.X. See if it clears things up.
Hmm... that sounds like an ugly bug. If that's the case, I'm relieved
to hear it, because I was beginning to wonder if I was going slightly
I'll try checking out the latest apr/apr-util/httpd and rebuilding
the whole show... Hopefully that clears up the problem. Either way,
I'll report back with the results.
Thanks for the quick response and keep up the awesome work, Ben (and
the rest of the SVN team).
Received on Wed Jun 22 23:54:21 2005