[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn client with ssh: data loss in output when both stdout and stderr are redirected to a pipe

From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 30 May 2011 09:58:45 -0400

2011/5/30 Vincent Lefevre <vincent-svn_at_vinc17.net>:
> I've found the following bug with Subversion 1.6.16:
>  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627025
> The problem is: With the svn+ssh scheme, a ssh process is started and
> sets its stderr to non-blocking mode. When executing an API-based svn
> client with both stdout and stderr redirected to a pipe, output to
> stdout (and stderr too, I suppose) fails with EAGAIN instead of
> blocking when the pipe buffer is full. See the above URL for more
> information.
> "svn log 2>&1 | less" on a (big enough) svn+ssh working copy fails to
> output the full log. It sometimes ends with:
>  svn: Write error: Resource temporarily unavailable
> I think the above test should be sufficient, but just in case, I've
> attached (this is what I used for my Debian bug report):

This sounds similar to this bug:


Mark Phippard
Received on 2011-05-30 15:59:17 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.