git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lana Deere <lana.deere@gmail.com>
To: Jeff King <peff@peff.net>
Cc: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>, git@vger.kernel.org
Subject: Re: 2.37.2 can't "git pull" but 2.18.0 can
Date: Thu, 8 Sep 2022 12:46:14 -0400	[thread overview]
Message-ID: <CA+4x=b-SqzGfeTu4c8akk3quYF7ORZ5jYCpey5221H8=+_PfRg@mail.gmail.com> (raw)
In-Reply-To: <YxkI2zqCheqTv/wc@coredump.intra.peff.net>

With an explicit -c protocol.version=0 on the 2.37.2 git command line,
the pull is successful.  For what it's worth, the server git is still
2.18.0 in all of these cases.  Only the client side is being tested so
far.  I will try to gather the packet traces and see if there's a
problem sharing them.  Will this mailing list allow attachments?

.. Lana (lana.deere@gmail.com)



On Wed, Sep 7, 2022 at 5:10 PM Jeff King <peff@peff.net> wrote:
>
> On Wed, Sep 07, 2022 at 02:53:37PM -0400, Lana Deere wrote:
>
> > OK, I tried the bisect again.  I used the bin-wrappers/git from my git
> > source each time I did a pull and each time I did a bisect.  This time
> > the final result was indeed different:
> >
> > $ ~/tmp/git/git/bin-wrappers/git bisect bad
> > eb049759fb6b739310af52ee0e13ce6cd0c86be7 is the first bad commit
> > commit eb049759fb6b739310af52ee0e13ce6cd0c86be7
> > Author: Jeff King <peff@peff.net>
>
> Drat, I shouldn't have helped you figure out I was the culprit. ;)
>
> >     protocol: re-enable v2 protocol by default
>
> OK, so this is definitely a plausible bisection result. Things shouldn't
> behave any different between the two protocols, but there could be a
> bug.
>
> The first thing I'd try is whether:
>
>   .../git/2.37.2/bin/git -c protocol.version=0 pull
>
> works like 2.18.0 does. If so, then that confirms that protocol v2 is
> the problem. At that point I might try capturing packet dumps with:
>
>   GIT_TRACE_PACKET=/tmp/v0.trace \
>   .../git/2.37.2/bin/git -c protocol.version=0 pull
>
>   GIT_TRACE_PACKET=/tmp/v2.trace \
>   .../git/2.37.2/bin/git -c protocol.version=2 pull
>
> They'll be sufficiently different that you can't just diff them, but if
> you're able to share them, one of us familiar with the protocol might be
> able to notice something.
>
> I don't _think_ there should be a problem with the server side of your
> connection speaking the v2 protocol. After all, you found that the
> ls-remote output was the same for both versions.
>
> -Peff

  reply	other threads:[~2022-09-08 16:46 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02 19:27 2.37.2 can't "git pull" but 2.18.0 can Lana Deere
2022-09-02 20:16 ` brian m. carlson
2022-09-06 18:26   ` Lana Deere
2022-09-07 12:59     ` Johannes Schindelin
2022-09-07 15:59       ` Lana Deere
2022-09-08 18:20       ` Jeff King
2022-09-03  1:07 ` Jeff King
2022-09-06 19:37   ` Lana Deere
2022-09-07  2:11     ` Đoàn Trần Công Danh
2022-09-07 15:56       ` Lana Deere
2022-09-07 18:21         ` Jeff King
2022-09-07 18:53           ` Lana Deere
2022-09-07 21:10             ` Jeff King
2022-09-08 16:46               ` Lana Deere [this message]
2022-09-08 18:14                 ` Jeff King
2022-09-08 19:23                   ` [PATCH 0/2] v2 protocol can't "git pull" with restricted refspec Jeff King
2022-09-08 19:24                     ` [PATCH 1/2] fetch: stop checking for NULL transport->remote in do_fetch() Jeff King
2022-09-08 19:26                     ` [PATCH 2/2] fetch: add branch.*.merge to default ref-prefix extension Jeff King
2022-09-08 20:36                       ` Junio C Hamano
2022-09-08 20:48                         ` Junio C Hamano
2022-09-09  2:17                           ` Jeff King
2022-09-09  5:23                             ` Junio C Hamano
2022-09-11  5:08                               ` Jeff King
2022-09-09 17:32                   ` 2.37.2 can't "git pull" but 2.18.0 can Lana Deere
2022-09-09 18:27                     ` Junio C Hamano
2022-09-12 14:58                       ` Lana Deere
2022-09-13  0:28                         ` Jeff King
2022-09-05 10:25 ` Johannes Schindelin
2022-09-06 18:38   ` Lana Deere
2022-09-07 10:20     ` Johannes Schindelin
2022-09-07 16:01       ` Lana Deere

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='CA+4x=b-SqzGfeTu4c8akk3quYF7ORZ5jYCpey5221H8=+_PfRg@mail.gmail.com' \
    --to=lana.deere@gmail.com \
    --cc=congdanhqx@gmail.com \
    --cc=git@vger.kernel.org \
    --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.
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).