git version 2.40.1.vfs.0.2
cpu: x86_64
built from commit: 59bc9667c84164a4ad879d9b424687ca631f01b3
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
Microsoft Windows [Version 10.0.19045.3086]
64-bit
These operations were performed in an administrative CMD prompt, though this hasn't been a problem in the past.
A single round of "Indexing objects" and "Resolving deltas" output, followed by the rest of the fetch and pull process.
The first pull took a bit longer than expected, and bounced between "Indexing objects" and "Resolving deltas" many times. Second pull was as expected.
(Despite the date on the prefetch being last week, this output was generated ~15 minutes ago. It's likely that this date is around the time I pulled last week though, Monday morning routines and whatnot 😄)
z:\og1\src>git pull
Prefetch 1686589283 (2023-06-12 17:01:23 +0000) (bytes received): 143024902, done.
Indexing objects: 100% (36693/36693), done.
Resolving deltas: 100% (23425/23425), done.
Indexing objects: 100% (54109/54109), done.
Resolving deltas: 100% (29450/29450), done.
Indexing objects: 100% (102788/102788), done.
Resolving deltas: 100% (68503/68503), done.
Indexing objects: 100% (35611/35611), done.
Resolving deltas: 100% (22965/22965), done.
Indexing objects: 100% (8623/8623), done.
Resolving deltas: 100% (5465/5465), done.
Indexing objects: 100% (12566/12566), done.
Resolving deltas: 100% (8385/8385), done.
Indexing objects: 100% (400/400), done.
Resolving deltas: 100% (222/222), done.
Indexing objects: 100% (332/332), done.
Resolving deltas: 100% (194/194), done.
Indexing objects: 100% (446/446), done.
Resolving deltas: 100% (189/189), done.
Indexing objects: 100% (1010/1010), done.
Resolving deltas: 100% (423/423), done.
Indexing objects: 100% (544/544), done.
Resolving deltas: 100% (168/168), done.
Indexing objects: 100% (975/975), done.
Resolving deltas: 100% (629/629), done.
Indexing objects: 100% (912/912), done.
Resolving deltas: 100% (418/418), done.
Indexing objects: 100% (911/911), done.
Resolving deltas: 100% (458/458), done.
Indexing objects: 100% (1883/1883), done.
Resolving deltas: 100% (1012/1012), done.
Indexing objects: 100% (1454/1454), done.
Resolving deltas: 100% (625/625), done.
Indexing objects: 100% (1479/1479), done.
Resolving deltas: 100% (893/893), done.
Indexing objects: 100% (1208/1208), done.
Resolving deltas: 100% (690/690), done.
Indexing objects: 100% (906/906), done.
Resolving deltas: 100% (487/487), done.
Indexing objects: 100% (614/614), done.
Resolving deltas: 100% (256/256), done.
Indexing objects: 100% (1323/1323), done.
Resolving deltas: 100% (784/784), done.
Indexing objects: 100% (1432/1432), done.
Resolving deltas: 100% (819/819), done.
Indexing objects: 100% (5396/5396), done.
Resolving deltas: 100% (2685/2685), done.
From https://dev.azure.com/office/Office/_git/Office
- [deleted] (none) -> [...]
or closed issue matching
what I'm seeing, including in the
git-for-windows/gittracker.Setup
microsoft/gitare you using? Is it 32-bit or 64-bit?Are you using Scalar or VFS for Git?
Scalar
to the issue you're seeing?
These operations were performed in an administrative CMD prompt, though this hasn't been a problem in the past.
Details
CMD
Minimal, Complete, and Verifiable example
this will help us understand the issue.
A single round of "Indexing objects" and "Resolving deltas" output, followed by the rest of the fetch and pull process.
The first pull took a bit longer than expected, and bounced between "Indexing objects" and "Resolving deltas" many times. Second pull was as expected.
(Despite the date on the prefetch being last week, this output was generated ~15 minutes ago. It's likely that this date is around the time I pulled last week though, Monday morning routines and whatnot 😄)
If the problem was occurring with a specific repository, can you specify
the repository?