I have observed some regressions with
log -v -g --xml http://server/repo/path
output in 1.6.15 that were not present in 1.6.13. I see a lot of -g
in this new version.
The client sees:
svn: REPORT of '/repo/!svn/bc/1234/path/in/repo': Could not read chunk
size: connection was closed by server (http://server)
The server logs:
[Wed Dec 15 15:48:18 2010] [error] [client 192.168.1.1] File not found:
revision 5678, path '/path/in/repo/file.txt' [404, #160013]
Now this particular file seems to have a long history of being deleted,
recreated with the same name, merged from multiple branches, etc., but
the merge info looks valid and the command runs without errors when
run against a 1.6.13 server.
I'll try and narrow down a test case, but was wondering if
anyone else had seen these errors logged or had ideas
on where the additional "file not found" check might
have been introduced.
Broken server 1.6.15 running under apache 2.2.17 over http.
Working server 1.6.13 running under apache 2.2.17 over http.
Client version does not seem to matter but tried 1.6.5,
1.6.12, and 1.6.15.
The "broken" server does appear to send about 2MB of xml
data before it dies. The "working" server sends 5MB of data.
It does not appear to be caused by a timeout, since it reliably
dies in exactly the same location every time.
Received on 2010-12-16 21:50:57 CET