On Sun, May 18, 2014 at 10:51 PM, Andy Bradford <amb-fos...@bradfords.org>wrote:
> Thus said Matt Welland on Sun, 18 May 2014 22:39:57 -0700: > > > We are still seeing this scenario. User education seems to have > > lessened the frequency a little. > > Are you still running a version of Fossil that does not have this fix: > > > http://www.fossil-scm.org/index.html/info/b4dffdac5e706980d911a0e672526ad461ec0640 > > Or have you upgraded the version of Fossil on the server and you are > still seeing this same error: > > Artifacts sent: 0 received: 895 Error: Database error: database is locked: > {UPDATE event SET mtime=(SELECT m1 FROM time_fudge WHERE mid=objid) WHERE > objid IN (SELECT mid FROM time_fudge);} > > Or are you seeing a different error? Or what are the typical causes for > the autosync failure that you encounter? > We are using 1.28 with that fix IIRC. I'll try to capture the exact autosync error when I see it next. The autosync fails happen when two or more people are trying to commit at the same time. One of them succeeds and the other fails with the do you want to continue message. If the user says yes then the commit completes and we have a fork. At least this is what I think is happening. > > Thanks, > > Andy > -- > TAI64 timestamp: 4000000053799c19 > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- Matt -=- 90% of the nations wealth is held by 2% of the people. Bummer to be in the majority...
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
