-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repeated Indexing Outputs/Resolving Deltas output when pulling after upgrading to 2.40.1.vfs.0.2 #585
Comments
Out of curiosity: what does |
Wow, I could have sworn I replied to this last week, but...maybe I only imagined it. Sorry for the slow reply... 😓
|
@AtOMiCNebula could you temporarily disable FSCache via |
Back from vacation, sorry for another slow reply! It does not appear to have changed things, unfortunately. I started a pull just now, forgot about this thread, came back to it, hit CTRL+C right after a "Resolving Deltas" statement finished, disabled fscache, started the pull again, and it's still doing the back-and-forth. I'm not sure if the prefetch dates being different (despite running it seconds apart from each other) is a red herring or not. Perhaps something going wrong with packfile acquisition or processing? I saw #571 happen a release or two ago, but...well, I await your next suggestion for me to try. 😅
|
or closed issue matching
what I'm seeing, including in the
git-for-windows/git
tracker.Setup
microsoft/git
are 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?
The text was updated successfully, but these errors were encountered: