From: Jeff King <peff@peff.net>
To: Todd Zullinger <tmz@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: t5559 breaks with apache 2.4.55
Date: Thu, 26 Jan 2023 06:39:42 -0500 [thread overview]
Message-ID: <Y9Jmfg/jlSszVep4@coredump.intra.peff.net> (raw)
In-Reply-To: <Y81lQwG85+Skujja@pobox.com>
On Sun, Jan 22, 2023 at 11:33:07AM -0500, Todd Zullinger wrote:
> > So I haven't reported the bug further yet. But I thought I'd post this
> > here before anybody else wastes time digging in the same hole.
>
> FWIW, I think this is the same issue we discussed about 2
> months back, in <Y4fUntdlc1mqwad5@pobox.com>¹.
>
> I haven't done much else with it since then. It's almost
> surely either an apache httpd/mod_http2 or curl issue. If I
> had to bet, I'd say mod_http2. (But then, it could be curl
> and just has yet to be exposed widely because not many are
> using the current mod_http2 code.)
>
> ¹ https://lore.kernel.org/git/Y4fUntdlc1mqwad5@pobox.com/
Ah, I somehow completely forgot about that issue. Despite being one of
the two participants on the thread.
Yeah, after seeing that, I'm quite sure this is a mod_http2 issue. It
would be nice to bisect within the mod_http2 history to find the
culprit, but I'd first have to figure out how to build standalone apache
modules. ;)
I may try to poke at it later if I have time. It might also be worth
submitting a bug report to the mod_http2 folks. I'd hope to have a more
compact reproduction, but it does at least seem to fail reliably for me
(not even racily).
-Peff
next prev parent reply other threads:[~2023-01-26 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 8:00 t5559 breaks with apache 2.4.55 Jeff King
2023-01-22 16:33 ` Todd Zullinger
2023-01-26 11:39 ` Jeff King [this message]
2023-01-29 6:35 ` Jeff King
2023-02-09 21:45 ` Junio C Hamano
2023-02-11 2:20 ` Jeff King
2023-02-11 2:34 ` Junio C Hamano
2023-02-11 3:00 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y9Jmfg/jlSszVep4@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=tmz@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).