Adding progress information didn't help. I found a way to reproduce it reasonably reliably using just git, and bisected this to https://github.com/git/git/commit/eb049759fb6b739310af52ee0e13ce6cd0c86be7 which fixes the misbehaviour. (Even after that, the tip of git main still exhibits a similar hang if I force the use of protocol v0.)
However, this is definitely not something that can simply be cherry-picked to xenial's git, since none of the v2 stuff existed there. I think we may have to backport jammy's git to xenial.
Adding progress information didn't help. I found a way to reproduce it reasonably reliably using just git, and bisected this to https:/ /github. com/git/ git/commit/ eb049759fb6b739 310af52ee0e13ce 6cd0c86be7 which fixes the misbehaviour. (Even after that, the tip of git main still exhibits a similar hang if I force the use of protocol v0.)
However, this is definitely not something that can simply be cherry-picked to xenial's git, since none of the v2 stuff existed there. I think we may have to backport jammy's git to xenial.