Re: svn log fails (invalid xml) when piped to less

On 2004-03-09 00:05+0000, Julian Foad wrote:
>
> What can be the difference between those two invocations? The pipe to
> "less" can get broken if you quit from "less", but that normally gives a
> different error so I assume you are scrolling to the end of the
> file.

yep.

> If you pipe the output to a program like "tail" that reads all of
> the input but doesn't interact with the user, does the same happen?

No, nothing with tail, head, grep or sed. I used less following way:
"read" the first page, and after that start scrolling down with
space, until I reach revision 772 when this error happens.

And if I checkout the repository out of via https:// the problem will
vanish. Also if I try that in my home machine, I could not reproduce
it. (The machine where this happens is Debian/woody, subversion has
been installed from here:
http://people.debian.org/~cjwatson/subversion-woody/)

Also, if I convert that cvs repository with correct encoding,
converted svn-repo will behave ok.

svn produced this error message:

svn: REPORT request failed on '/svn/test/!svn/bc/883/trunk'
svn: The REPORT request returned invalid XML in the response: XML
parse error at line 971: Bytes: 0xEF 0x00 0x00 0x00

Here is ethereal trace (part) of troublesome connection:
...
    107 REPORT /svn/test/!svn/bc/883/trunk HTTP/1.1
    108 Host: localhost:8080
    109 User-Agent: SVN/1.0.0 neon/0.24.4
    110 Connection: TE
    111 TE: trailers
    112 Content-Length: 135
    113 Content-Type: text/xml
    114 Authorization: Basic XXXXXXXXXXXXXXXX
    115
    116 <S:log-report xmlns:S="svn:"><S:start-revision>883</S:start-revision><S:end-revision>1</S:end-revision><S:path></S:path></S:log-report>HTTP/1.1 200 OK
    117 Date: Tue, 09 Mar 2004 02:48:28 GMT
    118 Server: Apache/2.0.48 (Debian GNU/Linux) DAV/2 SVN/1.0.0 mod_ssl/2.0.48 OpenSSL/0.9.6c
    119 Transfer-Encoding: chunked
    120 Content-Type: text/xml; charset="utf-8"
    121
    122 1f43
    123 <?xml version="1.0" encoding="utf-8"?>
    124 <S:log-report xmlns:S="svn:" xmlns:D="DAV:">
    125 <S:log-item>
...
(Log output will stop before r771, r772 is last one that I could see)
...
   1071 <S:log-item>
   1072 <D:version-name>771</D:version-name>
...
   1084 4. Ilmoittautumisj�rjestys. L�ht�aikojen ja joukkuenumeroiden jakamisen
   1085 j�lkeen ilmoittautuneet l�htev�t mahd. peruutuspaikoilla tai
   1086 viimeisen�.
   1087 -https://... <clear ascii data follows>

Line 1086 is '76 69 69 6d 65 69 73 65 6e ef bf bd 2e 0a'.

> It may be another story, but it may be related to this problem. Are the
> non-ASCII characters in log messages, in file names, or in file contents?

Both, in log messages and in file contents.

> As usual, if you could make a small reproduction recipe, that would be
> great.

I can't reproduce that myself elsewhere than in that particular
machine. =( So it seems that there is something wrong with interaction
between pipes, less and subversion in that machine. Any ideas where to
look or is this worth of digging more?

Thanks,
Jani

-- 
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org