Update checkin lock-timeout
(1) By anonymous on 2021-10-08 15:35:58 [source]
As the text says, it can change and it did, so here the update for the documentation:
Index: www/sync.wiki
==================================================================
--- www/sync.wiki
+++ www/sync.wiki
@@ -718,11 +718,11 @@
If some other client has already indicated that it was also
trying to commit against CHECKIN-HASH, that indicates that a
fork is about to occur, and the server will reply with
a "ci-lock-fail" pragma (see below). Check-in locks
automatically expire when the check-in actually occurs, or
-after a timeout (currently 24-hours but subject to change).
+after a timeout (currently one minute but subject to change).
<li><p><b>ci-lock-fail</b> <i>LOGIN MTIME</i></p>
<p>When a server receives two or more "ci-lock" pragma messages
for the same check-in but from different clients, the second a
subsequent ci-lock will provoke a ci-lock-fail pragma in the
(2) By Stephan Beal (stephan) on 2021-10-08 17:54:31 in reply to 1 [link] [source]
As the text says, it can change and it did, so here the update for the documentation:
Thank you for the report and patch. That and the text/json
references (presumably also from you?) have been fixed.