Re: Fetching 24 Linux commits = 1.2 GiB

[Jiri Slaby <jslaby@suse.cz>]

On 15. 04. 20, 15:56, Konstantin Ryabitsev wrote:
> On Wed, Apr 15, 2020 at 10:01:46AM +0200, Jiri Slaby wrote:
>> Hi,
>>
>> I was at 8f3d9f354286 of:
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>
>> I did git remote update today and it fetched:
>> Receiving objects: 100% (7330823/7330823), 1.20 GiB
>> It updated master: 8f3d9f354286..8632e9b5645b, that is 24 small commits.
>>
>> One colleague of mine fetched 1324 commits:
>> Receiving objects: 100% (6820/6820), 4.21 MiB | 6.70 MiB/s, done.
>> Resolving deltas: 100% (5114/5114), completed with 1035 local objects.
>> From git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
>>    7e63420847ae..8632e9b5645b  master     -> origin/master
>>
>> Another colleague fetched the same what I and:
>>   Receiving objects: 100% (7330823/7330823), 1.20 GiB
>> too.
>>
>> I did git gc --prune && git prune now and I am at 1.7G back from 3.5 G.
>>
>> Is that a bug? What info should I provide?
> 
> I've helped sfr troubleshoot the same issue last week -- it's most 
> likely due to 2.26 turning on protocol version=2 by default.  
> Unfortunately, reproducing this has been tricky, so if you can reliably 
> make this happen again, then providing a full copy of your local tree as 
> well as the remote you're trying to fetch may greatly help narrow it 
> down.

I tried hard, but cannot reproduce. I noticed a difference between
2.25.1 and 2.25.1+protocol.version=2, though:

$ git config protocol.version 1 # the default in 2.25
$ git fetch
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
8f3d9f354286745c751374f5f1fcafee6b3f3136
error: Server does not allow request for unadvertised object
8f3d9f354286745c751374f5f1fcafee6b3f3136
$ git config protocol.version 2
$ git fetch
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
8f3d9f354286745c751374f5f1fcafee6b3f3136
remote: Enumerating objects: 1433262, done.
...

Doing fetch v5.7-rc1 (which is 8f3d9f3 above) with proto 1 works. So the
server obviously advertises different set of objects with proto 1 and 2.

thanks,
-- 
js
suse labs