Skip to content
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

Actually switch to "Resolving Deltas" #4080

Merged
merged 1 commit into from
Nov 15, 2024
Merged

Conversation

Keno
Copy link
Member

@Keno Keno commented Nov 8, 2024

Libgit2's "Resolving Deltas" code is extremely slow (libgit2/libgit2#4674) on larger repositories, so it is important to have an accurate progress bar to avoid users thinking the download is stuck. We had this implemented. However, we were never actually switching to it, because the progress meter thought the progress was jumping backwards and wouldn't actually update because of it. Fix that by resetting it on the first switch to resolving deltas.

Libgit2's "Resolving Deltas" code is extremely slow (libgit2/libgit2#4674) on
larger repositories, so it is important to have an accurate progress bar to avoid users thinking
the download is stuck. We had this implemented. However, we were never actually switching to it,
because the progress meter thought the progress was jumping backwards and wouldn't actually update
because of it. Fix that by resetting it on the first switch to resolving deltas.
@KristofferC
Copy link
Member

I have been wondering why I never saw this... I thought it was just too fast I think 😆

@IanButterworth
Copy link
Member

Merge?

@KristofferC KristofferC merged commit 87a4a91 into master Nov 15, 2024
7 checks passed
@KristofferC KristofferC deleted the kf/resolvingdeltasprogress branch November 15, 2024 15:07
IanButterworth pushed a commit that referenced this pull request Nov 24, 2024
Libgit2's "Resolving Deltas" code is extremely slow (libgit2/libgit2#4674) on
larger repositories, so it is important to have an accurate progress bar to avoid users thinking
the download is stuck. We had this implemented. However, we were never actually switching to it,
because the progress meter thought the progress was jumping backwards and wouldn't actually update
because of it. Fix that by resetting it on the first switch to resolving deltas.

(cherry picked from commit 87a4a91)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants