Stephan, Although I haven't been able to consistently reproduce the errors. These were definitely not network errors.
The steps involve. 1) Client A makes a commit. 2) Client B makes a commit - but is warned that they will fork. 3) Client B updates - but doesn't appear to get Client A's commit. 4) Client B commits with no error and the server forks. 5) Client C updates but only gets Client A or B's commit but not both. At this point fossil rebuild on the server. Clients can update and can see the other leafs. On Sun, Aug 18, 2013 at 10:58 AM, Stephan Beal <sgb...@googlemail.com>wrote: > On Sun, Aug 18, 2013 at 7:35 PM, Clive Hayward <haywa...@chayward.com>wrote: > >> Michai, >> >> In more than one instance a subsequent commit was performed on one of the >> clients (unaware that there was an issue). That commit was visible to the >> other client only after the server repository was rebuilt. >> > > i've had a couple cases which sound similar but were explainable. i would > make a commit, the push would fail because my network was out or whatever, > and i wouldn't notice it. Later on i'd wonder where my commit was. That's > happened to me a handful of times over the years. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > -- Clive Hayward
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
