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

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:

http://subversion.tigris.org/issues/show_bug.cgi?id=3014

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/