RE: Git push --mirror hangs

[Joonas Harjumaki <joonas.harjumaki@fi.abb.com>]

Thanks! Pushing the history in parts helped.

Joonas Harjumäki

-----Original Message-----
From: brian m. carlson <sandals@crustytoothpaste.net> 
Sent: tiistai 20. huhtikuuta 2021 4.26
To: Joonas Harjumaki <joonas.harjumaki@fi.abb.com>
Cc: git@vger.kernel.org
Subject: Re: Git push --mirror hangs

On 2021-04-19 at 17:11:01, Joonas Harjumaki wrote:
> Git has been stuck for an hour and half after printing these:
> Writing objects: 100% (116519/116519), 3.69 GiB | 2.99 MiB/s, done.
> Total 116519 (delta 74981), reused 116519 (delta 74981), pack-reused 0
> 18:42:45.650572 trace.c:487             performance: 1266.567544063 s: git command: /usr/lib/git-core/git pack-objects --all-progress-implied --revs --stdout --thin --progress
> 18:42:45.743254 pkt-line.c:80           packet:          git> 0000
> 18:42:46.465637 http.c:703              <= Recv header, 0000000013 bytes (0x0000000d)
> 18:42:46.465693 http.c:715              <= Recv header: HTTP/2 200
> 18:42:46.465707 http.c:703              <= Recv header, 0000000024 bytes (0x00000018)
> 18:42:46.465716 http.c:715              <= Recv header: cache-control: private
> 18:42:46.465727 http.c:703              <= Recv header, 0000000053 bytes (0x00000035)
> 18:42:46.465734 http.c:715              <= Recv header: content-type: application/x-git-receive-pack-result
> 18:42:46.465744 http.c:703              <= Recv header, 0000000124 bytes (0x0000007c)
> 18:42:46.465752 http.c:715              <= Recv header: p3p: CP="CAO DSP COR ADMa DEV CONo TELo CUR PSA PSD TAI IVDo OUR SAMi BUS DEM NAV STA UNI COM INT PHY ONL FIN PUR LOC CNT"
> 18:42:46.465763 http.c:703              <= Recv header, 0000000055 bytes (0x00000037)
> 18:42:46.465770 http.c:715              <= Recv header: x-tfs-processid: [stripped]
> 18:42:46.465778 http.c:703              <= Recv header, 0000000064 bytes (0x00000040)
> 18:42:46.465785 http.c:715              <= Recv header: strict-transport-security: max-age=31536000; includeSubDomains
> 18:42:46.465795 http.c:703              <= Recv header, 0000000050 bytes (0x00000032)
> 18:42:46.465801 http.c:715              <= Recv header: activityid: [stripped]
> 18:42:46.465810 http.c:703              <= Recv header, 0000000053 bytes (0x00000035)
> 18:42:46.465833 http.c:715              <= Recv header: x-tfs-session: [stripped]
> 18:42:46.465842 http.c:703              <= Recv header, 0000000051 bytes (0x00000033)
> 18:42:46.465849 http.c:715              <= Recv header: x-vss-e2eid: [stripped]
> 18:42:46.465858 http.c:703              <= Recv header, 0000000082 bytes (0x00000052)
> 18:42:46.465866 http.c:715              <= Recv header: x-vss-userdata: [stripped]
> 18:42:46.465899 http.c:703              <= Recv header, 0000000029 bytes (0x0000001d)
> 18:42:46.465910 http.c:715              <= Recv header: x-frame-options: SAMEORIGIN
> 18:42:46.465919 http.c:703              <= Recv header, 0000000068 bytes (0x00000044)
> 18:42:46.465926 http.c:715              <= Recv header: request-context: [stripped]
> 18:42:46.465936 http.c:703              <= Recv header, 0000000048 bytes (0x00000030)
> 18:42:46.465945 http.c:715              <= Recv header: access-control-expose-headers: Request-Context
> 18:42:46.465954 http.c:703              <= Recv header, 0000000033 bytes (0x00000021)
> 18:42:46.465961 http.c:715              <= Recv header: x-content-type-options: nosniff
> 18:42:46.465972 http.c:703              <= Recv header, 0000000104 bytes (0x00000068)
> 18:42:46.465980 http.c:715              <= Recv header: x-msedge-ref: [stripped]
> 18:42:46.465990 http.c:703              <= Recv header, 0000000037 bytes (0x00000025)
> 18:42:46.465996 http.c:715              <= Recv header: date: Mon, 19 Apr 2021 15:42:45 GMT
> 18:42:46.466009 http.c:703              <= Recv header, 0000000002 bytes (0x00000002)
> 18:42:46.466017 http.c:715              <= Recv header:
> 18:42:46.466294 pkt-line.c:80           packet:     sideband< \2\15Analyzing objects... (41535/116519)
> remote:

I suspect by the content of this sideband packet, that Azure DevOps is doing something with those objects.  The text "Analyzing objects"
doesn't appear in Git, so it's presumably some operation specific to Azure DevOps that's being performed.

I would ask them what's going on on their side that's making this so slow.  It's possible that waiting will help, but it's also possible that it won't.  Since I don't know what's actually happening on the server side, I can't say.
--
brian m. carlson (he/him or they/them)
Houston, Texas, US