I've isolated the problem. (Not solved it, but identified it.) The problem was network congestion somewhere between China and wherever sqlite.org is located. After I did a complete shutdown of everything and restarted from scratch (renegotiating my PPPoE lease) the problem went away by itself. Further what was taking literally hours before only took a few minutes this time.
So... It seems that Fossil is being a little bit optimistic about the network's reliability. Given the random locations that things were dying in, I'm guessing there was network timeouts that weren't being gracefully handled (as in reported) causing Fossil to process incomplete sets of cards. 2009/8/13 D. Richard Hipp <[email protected]> > > On Aug 12, 2009, at 11:12 PM, Michael Richter wrote: > > 2009/8/13 D. Richard Hipp <[email protected]> >> Can I call you and see your screen via VNC or something. I'll bet we can >> get to the bottom of this really quick that way... >> >> Interesting question. I'm not sure if I'm open to VNC (nor if I have it >> installed even). Let me run some tests. I'll be back in touch in a few. >> (Minutes or hours. Your choice.) >> > > It is late here. Everything is working great for me. I'll sorry it is not > working for you. I really have no idea what might be wrong. Please try to > look at things in the debugger to see what is going on. Simply set a > breakpoint on the spot where the error occurs. I'm going to get some > sleep.... > > > D. Richard Hipp > [email protected] > > > >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
