From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Lukas Fleischer <lfleischer@lfos.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Mark remote `gc --auto` error messages
Date: Thu, 2 Jun 2016 17:53:18 -0400 [thread overview]
Message-ID: <20160602215317.GC13356@sigill.intra.peff.net> (raw)
In-Reply-To: <CAPc5daXVx1=ptsKJEfEzXbjCNvwYxjAPyp_pob9CeR+Qr3tG_g@mail.gmail.com>
On Thu, Jun 02, 2016 at 01:14:02PM -0700, Junio C Hamano wrote:
> > What exactly are you referring to (you only quoted the introduction)?
> > Do you think we should fix the git-gc issue but keep the general
> > behavior of printing messages unaltered? Do you think it would be
> > worthwhile to make server messages distinguishable in general?
>
> The latter, which I think was what your implementation was attempting to do
> if I read it correctly.
And btw, I don't think this patch fixes the general case. E.g., if
receive-pack hits any of its die("BUG") lines, they will not be
prefixed. Most clients wouldn't see them, but ssh ones would.
To fix that you'd have to do a whole async process wrapping
`receive-pack` that just reads its stdout and stderr and muxes it back
over the sideband. But I can think of two roadblocks there:
- I think the original design of receive-pack was _not_ to share all
of stderr with the user, because it might contain secret-ish
server-side things. That's why we have rp_error() which copies to
the sideband.
I don't know how useful that is in practice. We copy the stderr
wholesale from sub-processes like index-pack, so things like file
paths are likely to get leaked there.
- the implementation is a bit tricky, because the die() will take
down the mux thread, too.
-Peff
next prev parent reply other threads:[~2016-06-02 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 19:05 Mark remote `gc --auto` error messages Lukas Fleischer
2016-06-02 19:33 ` Junio C Hamano
2016-06-02 20:06 ` Lukas Fleischer
2016-06-02 20:14 ` Junio C Hamano
2016-06-02 21:48 ` Jeff King
2016-06-02 21:59 ` Junio C Hamano
2016-06-02 22:04 ` Jeff King
2016-06-02 21:53 ` Jeff King [this message]
2016-06-05 9:36 ` [PATCH] receive-pack: send auto-gc output over sideband 2 Lukas Fleischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160602215317.GC13356@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=lfleischer@lfos.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).