fix(repository): immediately re-clone on pull failure#844
Closed
arnaud-dezandee wants to merge 1 commit intopadok-team:mainfrom
Closed
fix(repository): immediately re-clone on pull failure#844arnaud-dezandee wants to merge 1 commit intopadok-team:mainfrom
arnaud-dezandee wants to merge 1 commit intopadok-team:mainfrom
Conversation
Contributor
Author
|
I did some more testing and this does not fix all issues I see on my deployment. Here is a log extract Will try #783 and see if that solves it |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix the git bundle flow to immediately re-clone and retry when a pull fails (e.g. after a force-push), instead of returning an error and deferring recovery to the next reconciliation cycle.
Bundlelogic intobundleWithRetry(ref, isRetry)to support a single retrybundleWithRetrywithisRetry=true