On Fri, Oct 28, 2011 at 8:10 PM, Richard Hipp <[email protected]> wrote:
> The statement appears to be purely defensive, so I'm guessing we could take
> it out . But it would also be good to understand what is going on.
>
> When you do the auto-sync, are you doing it from an account that is
> read-only ("anonymous")? Maybe we are opening the database in read-only
> mode for a pull and hence this attempt to clean up a table in the database
> is failing - just a guess.
>
Every time i've seen it has been with a r/w account, and i _think_ i've only
seen it on the main repo. i've always attributed it to other activity going
on concurrently in the main repo, but now that i see it's a local error i
have no idea what might cause it, especially since fossil doesn't use any
threads or forked processes in a sync operation (from what i understand
fork() is only used in server mode).
It's nothing tragic, just something that pops up every couple of weeks or
so.
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
