git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: andrey a <gvozdila@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: bug while cloning http repo
Date: Mon, 7 Nov 2022 19:26:35 -0500	[thread overview]
Message-ID: <Y2miO01QqsL/mvIm@nand.local> (raw)
In-Reply-To: <CAOvKmB_qjAm66fAuDBmgGQG7J=+=VW6Fayxfp1zPs5qJfdd=-Q@mail.gmail.com>

On Mon, Nov 07, 2022 at 07:58:03PM +0300, andrey a wrote:
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
>
> What did you do before the bug happened? (Steps to reproduce your issue)
>
> git clone http://git.altlinux.org/gears/r/rust.git
>
>
> What did you expect to happen? (Expected behavior)
>
> Normal cloned repo appears.
>
> What happened instead? (Actual behavior)
>
> git clone http://git.altlinux.org/gears/r/rust.git
> Cloning into 'rust'...
> error: Unable to get pack file
> http://git.altlinux.org/gears/r/rust.git/objects/pack/pack-42e36950f8cd6e0d242719691491d16dd2e270e6.pack
> transfer closed with 7043414950 bytes remaining to read

It looks like something (e.g., firewall, anti-virus software) between
your workstation and git.altlinux.org is terminating the connection
earlier than it should be.

So your client is only getting part of the pack that it asked for, and
some of the objects appear missing.

> Looks like versions before 2.33.4 works fine. And after 2.33.5 (and
> 2.34.1 2.35.1) reproduce bug.

If there is a bisection which conclusively points to a single commit,
that would be interesting to know. That might not necessarily indicate a
bug in Git, but instead a behavior change which tickles whatever
mechanism is sitting on either side of the connection.

Thanks,
Taylor

      reply	other threads:[~2022-11-08  0:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 16:58 bug while cloning http repo andrey a
2022-11-08  0:26 ` Taylor Blau [this message]

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=Y2miO01QqsL/mvIm@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gvozdila@gmail.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).