From: Beat Bolli <dev+git@drbeat.li>
To: David <courrier@david-kremer.fr>, git@vger.kernel.org
Subject: Re: Severe Regression in Git 1.21.0 -- not receiving any data
Date: Fri, 31 May 2019 21:18:51 +0200 [thread overview]
Message-ID: <a6a0e1be-8450-e61c-fe1c-911831004f66@drbeat.li> (raw)
In-Reply-To: <04a82e31-2292-ef73-98c5-b9a5ff28e000@david-kremer.fr>
On 31.05.19 13:31, David wrote:
> # Summary
>
> I was trying to clone the AOSP source tree (Android Open Source Project)
> and I finally was able to formally identify what seems to be a severe
> regression (one that is blocking usage) in the last version of git
> (2.21.0).
>
> # Steps to reproduce
>
> The AOSP projects recommend to use ubuntu 14.04 as its build platform.
> The git version for this distro is :
>
> ```
> root@eb57f366840e:/android# git --version
> git version 1.9.1
> ```
>
> In a docker image for this OS, I am able to execute:
>
> ```
> root@eb57f366840e:~# git clone
> https://android.googlesource.com/platform/manifest
> Cloning into 'manifest'...
> remote: Sending approximately 39.94 MiB ...
> remote: Counting objects: 852, done
> remote: Finding sources: 100% (27/27)
> remote: Total 16017 (delta 4968), reused 16017 (delta 4968)
> Receiving objects: 100% (16017/16017), 39.65 MiB | 9.04 MiB/s, done.
> Resolving deltas: 100% (4968/4968), done.
> Checking connectivity... done.
> ```
>
> Now, on my local Archlinux Box, the git version is 2.21.0 (latest).
>
> The same command:
>
> ```
>
> git clone https://android.googlesource.com/platform/manifest
> ```
>
> Is launching a single thread that uses 100% of one CPU core FOREVER,
> until a timeout arises after like 40 minutes (the remote hung up
> unexpectedly). Someone on the #git channel (irc.freenode.net) was able
> to reproduce the exact same behaviour.
>
> I must add that this of course arises only with the repo I mention in
> this email (github repositories are just fine). So probably a mismatch
> in protocol between git server/client ? Anyways, I'm far from having the
> skills to fix that thing.
>
> I hope this report is useful, and in any case, I would like to know
> about the possible outcomes of this report.
>
> I would be actually very surprised if someone did not notice that
> before, given that the latest git version is from february, but I can
> try anyway :)
>
> Cheers,
>
> David
Can you try
GIT_TRACE_PACKET=/tmp/packet.txt GIT_TRACE=/tmp/trace.txt git clone
https://android.googlesource.com/platform/manifest
?
The new files in /tmp help you see where the operation stalls.
Warning: the output will be large!
Beat
prev parent reply other threads:[~2019-05-31 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 11:31 Severe Regression in Git 1.21.0 -- not receiving any data David
2019-05-31 19:18 ` Beat Bolli [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=a6a0e1be-8450-e61c-fe1c-911831004f66@drbeat.li \
--to=dev+git@drbeat.li \
--cc=courrier@david-kremer.fr \
--cc=git@vger.kernel.org \
/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).