Re: issue upgrading git from 1.8.2.1 to 2.8.0

On Sat, Apr 23, 2016 at 01:18:50AM -0400, Gennaro Torre wrote:

This is what I see:

01:16:15.789969 pkt-line.c:80           packet:        fetch>
git-upload-pack /tumblr.git\0host=<cache>\0
01:16:15.851231 pkt-line.c:80           packet:        fetch<
a210029455476c3ae0d34748aeaeccf71864fd81 HEAD\0multi_ack thin-pack
side-band side-band-64k ofs-delta shallow no-progress include-tag
multi_ack_detailed symref=HEAD:refs/heads/master agent=git/2.8.0
01:16:15.851433 pkt-line.c:80           packet:        fetch<
511b1feab8d10b81777a75c02dabc94c7da9e0d4 refs/heads/263-fix
.....
01:17:59.497259 pkt-line.c:80           packet:        fetch<
cd63ca15d47b469e692faea2e04f32a241a6637a refs/tags/hotposts_v0.1
01:17:59.497265 pkt-line.c:80           packet:        fetch<
4749ee8a11ca093928c8a43fb0147d22177f1d71 refs/tags/hotposts_v0.1^{}
01:17:59.497282 pkt-line.c:80           packet:        fetch< 0000
Server supports multi_ack_detailed
Server supports side-band-64k
Server supports ofs-delta
Server version is git/2.8.0

So that's weird. The client gets the initial ref advertisement and
then...does nothing? It should drop into find_common() and start sending
want/have lines to the server (or decide it doesn't need any objects and
immediately send a flush packet).

Is the client chewing any CPU, or otherwise doing anything according to
"strace"? Is it possible to connect to it with gdb and get a backtrace?

-Peff