On Wed, Apr 16, 2014 at 9:14 AM, Stephan Beal <sgb...@googlemail.com> wrote:
>
> On Wed, Apr 16, 2014 at 6:01 PM, Matt Welland <estifo...@gmail.com> wrote:
>
>> 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);}
>> Round-trips: 1 Artifacts sent: 0 received: 0
>> Pull finished with 360 bytes sent, 280 bytes received
>> Autosync failed
>> continue in spite of sync failure (y/N)? n
>>
>> Could fossil silently retry a couple times instead of giving up so easily?
>>
>> If the user says y and continues then we get forks in the timeline which
>> are very confusing to non-experts.
>>
>
> Isn't the db being locked a sign that a fork is almost eminent? If someone
> is writing to the repo and that lock is blocking your autosync, then a fork
> has possibly already happened (or will if autosync retries, either
> automatically or because the user tapped Y).
>
Yes, exactly. Presumably a commit from someone else is in progress. All
fossil has to do is wait a second and then try the sync again and then
report the "fossil will fork" message if appropriate or follow though with
the commit if the overlapping commit was on a different branch.
>
> --
> ----- stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal
> "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
> those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
>
> _______________________________________________
> 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
