Thus said "Ardie H. Hwang" on Thu, 04 Jun 2015 13:57:12 +0900: > I did not issue `fossil push` because I wasn't sure whether the local > repo is in stable state or not, although the error occurred at sync > phase.
Based on the output you provided, Fossil hit an assertion during opening a connection. The local repository should be in a fine state. You could always run ``fossil test-integrity'' on the repository if you're still uncertain. Fossil would have a pretty major bug indeed if a network related problem caused your repository to be unstable. However, the fact that you hit the assert means there may actually be a bug, but not one that would impact the integrity of your repository. Andy -- TAI64 timestamp: 4000000055706dc5 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
