From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2] receive-pack: fix stale packfile locks when dying
Date: Fri, 10 Mar 2023 12:49:04 +0100 [thread overview]
Message-ID: <ZAsZMAhgag1iBSK5@ncase> (raw)
In-Reply-To: <ZArvkVPhF4Th424Z@coredump.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
On Fri, Mar 10, 2023 at 03:51:29AM -0500, Jeff King wrote:
> On Fri, Mar 10, 2023 at 07:52:10AM +0100, Patrick Steinhardt wrote:
[snip]
> > builtin/receive-pack.c | 14 ++++++++++----
> > 1 file changed, 10 insertions(+), 4 deletions(-)
>
> There's no test here, and I think we _could_ make a reliable one with
> something like:
>
> 1. Have a proc-receive hook that signals via fifo that it's running,
> then pauses indefinitely.
>
> 2. Start a push in the background, then wait on the fifo signal.
>
> 3. Kill receive-pack.
>
> But it's awfully complicated for little gain. I'm fine with not worrying
> about it (and I did something similar manually to make to sure it works
> as we expect).
I actually tried doing exactly what you're proposing here yesterday. It
caused hangs, lingering processes, you had to play games to not trigger
the &&-chain linter due to the backgrounding via &, and ultimately it
somehow just didn't work.
So at some point I came to the same conclusion as you did, that it's
just too complicated for little gain.
Thanks.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-10 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 13:09 [PATCH] receive-pack: fix stale packfile locks when dying Patrick Steinhardt
2023-03-09 15:59 ` Jeff King
2023-03-10 6:24 ` Patrick Steinhardt
2023-03-10 8:37 ` Jeff King
2023-03-09 18:26 ` Taylor Blau
2023-03-09 18:48 ` Junio C Hamano
2023-03-09 18:49 ` Junio C Hamano
2023-03-10 6:52 ` [PATCH v2] " Patrick Steinhardt
2023-03-10 8:51 ` Jeff King
2023-03-10 11:49 ` Patrick Steinhardt [this message]
2023-03-10 13:20 ` Jeff King
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=ZAsZMAhgag1iBSK5@ncase \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.