git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Jeff King'" <peff@peff.net>
Cc: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: [Breakage] Git v2.21.0-rc0 - t5318 (NonStop)
Date: Fri, 8 Feb 2019 16:44:42 -0500	[thread overview]
Message-ID: <004a01d4bff7$8378daf0$8a6a90d0$@nexbridge.com> (raw)
In-Reply-To: <20190208210041.GA788@sigill.intra.peff.net>

On February 8, 2019 16:01, Jeff King wrote:
> On Fri, Feb 08, 2019 at 03:38:05PM -0500, Randall S. Becker wrote:
> 
> > > Exactly (if we even care about them being NULs; otherwise, we can
> > > omit the "tr" invocation).
> >
> > I'm a bit perplexed about this... Obviously added some debugging info,
> > but why we're getting No REQUEST_METHOD is perplexing. Is this a lack
> > of an apache2 instance?
> 
> No, this shouldn't be using apache at all. But...
> 
> > expecting success:
> >         NOT_FIT_IN_SSIZE=$(ssize_b100dots) &&
> >         env \
> >                 CONTENT_TYPE=application/x-git-upload-pack-request \
> >                 QUERY_STRING=/repo.git/git-upload-pack \
> >                 PATH_TRANSLATED="$PWD"/.git/git-upload-pack \
> >                 GIT_HTTP_EXPORT_ALL=TRUE \
> >                 REQUEST_METHOD=POST \
> >                 CONTENT_LENGTH="$NOT_FIT_IN_SSIZE" \
> >                 yes | tr "y" "\\0" | git http-backend 2>err &&
> >         echo "Err is" &&
> >         cat err &&
> >         grep "fatal:.*CONTENT_LENGTH" err
> >
> > Status: 500 Internal Server Error
> > Expires: Fri, 01 Jan 1980 00:00:00 GMT
> > Pragma: no-cache
> > Cache-Control: no-cache, max-age=0, must-revalidate
> >
> > Err is
> > fatal: No REQUEST_METHOD from server
> > not ok 15 - CONTENT_LENGTH overflow ssite_t
> 
> The problem is that you're setting the environment now for "yes". You'd
> need:
> 
>   yes | tr "y" "\\0" | env \
>     CONTENT_TYPE=... \
>     REQUEST_METHOD=POST \
>     ...etc...
>     git http-backend

Aw crap. I feel really silly now. Thanks. Will advise.


  reply	other threads:[~2019-02-08 21:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 11:08 [Breakage] Git v2.21.0-rc0 - t5318 (NonStop) Randall S. Becker
2019-02-08 16:50 ` Jeff King
2019-02-08 17:49   ` Randall S. Becker
2019-02-08 18:03     ` Jeff King
2019-02-08 18:29       ` Johannes Sixt
2019-02-08 19:31         ` Junio C Hamano
2019-02-08 18:47       ` Randall S. Becker
2019-02-08 19:15         ` Jeff King
2019-02-08 19:26           ` Randall S. Becker
2019-02-08 19:31             ` Jeff King
2019-02-08 20:38               ` Randall S. Becker
2019-02-08 21:00                 ` Jeff King
2019-02-08 21:44                   ` Randall S. Becker [this message]
2019-02-08 22:07               ` brian m. carlson
2019-02-08 22:12                 ` Randall S. Becker
2019-02-08 22:18                   ` brian m. carlson
2019-02-08 22:36                     ` Randall S. Becker
2019-02-08 22:35                   ` Jeff King
2019-02-08 22:53                     ` Randall S. Becker
2019-02-09  4:24                       ` Jeff King
2019-02-09  8:39                         ` Johannes Sixt
2019-02-09 16:55                           ` Randall S. Becker
2019-02-09 23:29                           ` Jeff King
2019-02-10  9:40                             ` Johannes Sixt
2019-02-09 16:53                         ` Randall S. Becker

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='004a01d4bff7$8378daf0$8a6a90d0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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).