From 81841ec2856f62a8cadbc308b82293895c63edb2 Mon Sep 17 00:00:00 2001 From: Nasser Grainawi Date: Tue, 8 Dec 2020 08:35:17 -0700 Subject: Update git submodules * Update plugins/replication from branch 'stable-3.1' to c4df2f1eb9fe470debf4958e05cf29c2ec314b43 - Merge branch 'stable-3.0' into stable-3.1 * stable-3.0: Fix replication to retry on lock errors Change-Id: Ib4b2c1fcac5da6551f72bce68a101b93e9b43b19 - Merge branch 'stable-2.16' into stable-3.0 * stable-2.16: Fix replication to retry on lock errors Change-Id: I6e262d2c22d2dcd49b341b3c752d6d8b6c93b32c - Fix replication to retry on lock errors Versions of Git released since 2014 have created a new status "failed to update ref" which replaces the two statuses "failed to lock" and "failed to write". So, we now see the newer status when the remote is unable to lock a ref. Refer Git commit: https://github.com/git/git/commit/6629ea2d4a5faa0a84367f6d4aedba53cb0f26b4 Config 'lockErrorMaxRetries' is not removed as part of this change as folks who have it configured currently don't run into unexpected behavior with retries when they upgrade to a newer version of the plugin. Also, the "failed to lock" check is not removed for folks still using a version of Git older than 2014. Change-Id: I9b3b15bebd55df30cbee50a0e0c2190d04f2f443 --- plugins/replication | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/replication b/plugins/replication index e09b5a08e1..c4df2f1eb9 160000 --- a/plugins/replication +++ b/plugins/replication @@ -1 +1 @@ -Subproject commit e09b5a08e183d4f92410bfa06289a1784cefb43b +Subproject commit c4df2f1eb9fe470debf4958e05cf29c2ec314b43 -- cgit v1.2.3