From e746bd26b5830c998cd5091d11c542416b062e5f Mon Sep 17 00:00:00 2001 From: Nasser Grainawi Date: Tue, 8 Dec 2020 08:35:10 -0700 Subject: Update git submodules * Update plugins/replication from branch 'stable-3.0' to 2a600dede934b348173bff26e00f373367a3d142 - 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 4604b01e43..2a600dede9 160000 --- a/plugins/replication +++ b/plugins/replication @@ -1 +1 @@ -Subproject commit 4604b01e43c3b4aee3d03cb84945b3238c150ede +Subproject commit 2a600dede934b348173bff26e00f373367a3d142 -- cgit v1.2.3