Why does git need a network connection while "resolving deltas"?

user_292440 0
Viewed 727

When performing a git clone, git goes through the stages

  • Receiving objects
  • Resolving deltas
  • Checking out files

I would expect all of the network activity to be during Receiving objects, then Resolving deltas to be entirely local (as explained here What is git actually doing when it says it is "resolving deltas"?) but actually there is still a connection open.

I can tell this in two ways:

  1. Wireshark shows no activity during Resolving deltas then there are a few packets exchanged after along with closing the connection.
  2. Sometimes I see a connection closed by remote host during a long Resolving deltas step.

So what I'm interested in knowing is why git needs this connection to stay open during Resolving deltas? Is it needed after that for some reason (e.g. a hook)?

(note: this may depend on whether you are using https or ssh)

git
1 Answers

Given that this direction does not have anything left to do at this phase, it's not clear why Git keeps the transport protocol open until the resolving is done. In the other direction—if you're pushing—your Git has to keep the connection open during the receiver's resolution of the delivered thin pack, as the server-side reference updates have not yet occurred, while your own Git needs to know whether they are successful. So for push, your Git must hold the connection open, wait for the resolution to finish, and wait to see what their Git reports for the reference update phase.

For clone, however, their Git does not care whether your Git is able to update your references. It should be possible to close the transport earlier. There are probably some unfortunate code constructs that make this too difficult right now, that cause Git to keep the connection open instead.

user_12564520
Related