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

Jani Averbach wrote:
>
> svn log 2> /tmp/svn.err|less
> $ cat /tmp/svn.err
> svn: REPORT request failed on '/svn/kym/!svn/bc/882/trunk'
> svn: The REPORT request returned invalid XML in the response: XML
> parse error at line 971: Bytes: 0xEF 0x00 0x00 0x00
> . (/svn/kym/!svn/bc/882/trunk)
>
> However,
>
> $ svn log 2> /tmp/svn.err
> finished just fine.

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. 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? If not, how about "head" which will read a bit and then break the pipe? One of those would be better than "less" in a reproduction recipe.

Another possible difference between stdout to a pipe and stdout to the console is, on Windows at least, they can be using different character encodings. Are you running on Windows?

> The repository has been converted from cvs to svn by cvs2svn, and it
> contains a lot of ÖÄöä chars, which show up uncorrectly whith svn
> log, but that is another story.

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?

> I will try dig this more during next
> week, now I have to go to sleep.

As usual, if you could make a small reproduction recipe, that would be great. Also, it might be helpful to capture a trace of the comms protocol.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 9 01:04:51 2004