Hi guys, I'm enjoying playing with Fossil, but I've run into a problem... I have a satellite Internet connection. Apart from the incredible latency (over 1 second, testing with ping), my connection "freezes" every now and again.
This "freezing" problem has something to do with communication with the satellite, so it's not just my system. What happens is that the Internet is "dead" for awhile, maybe a minute, maybe longer. Anyway, I did a 'fossil commit' just as one of these "freezes" occurred, and I got this: # fossil commit -m "added file PKGS_MANAGEMENT" --nosign Autosync: http://bkhome.org/fossil/woof.cgi Bytes Cards Artifacts Deltas Send: 130 1 0 0 The freeze was temporary, a matter of seconds later the Internet was working again. However the 'fossil commit' operation was hung. I had to do a CTRL-C to terminate it. My question: Fossil should not be assuming a "perfect" Internet connection should it? Shouldn't a push (or pull) have a timeout, and maybe a retry? Just to hang is not very good. Then there's the question, as I had to terminate it with a CTRL-C, is there any kind of assurance that what did arrive at the remote repository, if anything, is not partial and thus corrupted? If I use a program like wget, it does have fallback code to handle this kind of situation. Regards, Barry Kauler _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
