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

Re: Broken pipe

From: Tobias Ringstrom <tobias_at_ringstrom.mine.nu>
Date: 2004-01-21 10:34:36 CET

Jack Repenning wrote:
> I think there's overwhelming precedent for suppressing the message. I
> tried a few commands, and couldn't find any that whine in these
> circumstances. For example:
> grep -lr . . | head
> find . | head

Yes and no. These commands are simple enough that they do not need to
shut down gracefully, so they do neither handle nor ignore SIGPIPE, and
are thus instantly killed by it. That's why there is not error message.

> Also interesting, these commands terminate quietly:
> svn stat --verbose | head
> svn ls -Rv | head
> svn info -R | head

That is because these commands are using printf without checking the
return value, which means that even if there is no more output, the
commands keep running until normal exit (or it's killed using e.g.
ctrl-c). We need to fix that. The status one is a bit harder to fix
because the print_status callback cannot not return an error.

> OTOH, I'm having a hard time seeing this as critical. If it were a month
> or two ago, I'd be all over suppressing the message; at this point, I'm
> feeling like I could live with that until 1.0.1 or so....

I agree. The lack of an error return value in the print_status callback
is... sigh... yet another API problem.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 21 10:35:11 2004

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.