Hey Richard, I get the same problem every once in awhile. Many times actually. I consider myself a heavy fossil user. My most active repository has 1087 checkins all made by me.
I once submitted a ticket about it here: http://www.fossil-scm.org/xfer/tktview/f7879271cf4182d2?plaintext I have not noticed a pattern with the syncing problems. Going by feel, it feels like it occurs most frequently when I create a new branch, or if I edit a check-in comment. Also keep in mind that I rarely if ever have had "sync errors". After every commit I would look at the remote repository to see if all the changes synced and they always do, except for these few cases. Also note that I always have auto-sync turned on. I used to host my repositories on a Linux VPS. I have since moved to Chisel and still have encountered sync problems. One time when the problem occured on my Linux VPS, I solved the problem by rebuilding the repository on the VPS side (the "host" repository). I dug around the source code of Fossil briefly to try and figure out the problem, and while I did not pinpoint it, I believed at the time that the issue had to do with the usage of clustered and unclustered artifacts. If I understand correctly, the used of these clusters is for a syncing optimization. However once I saw that you committed the --verily option, I stopped pursuing the problem because I was fairly confident that --verily solves the issue. Since my repository is hosted on Chisel, I will not find out until the next version is released and Chisel updates to that version. Also note that in ALL cases, the syncing problem can be solved by recloning the host repository. But I would prefer not to do that every time. I only used the fossil rebuild solution one time so I can't confidently say that it fixed the problem. And since I can't rebuild repositories on Chisel I can't try it with my current syncing problem. The problems have occured with and without HTTPS. So right now I actually have the syncing problem again. I created a new branch where I committed the entire source code to FreeType. This was done in a Linux VM. I then went to my Windows 8 desktop to update (keep in mind I have autosync always on) and it failed to pull the new branch; it's missing entirely from the timeline. It's also missing from my Macbook as well. So Mr. Hipp if you're interested, I can send you a copies of my repository to analyze and debug. However I would also need to get the current maintainer of Chisel to email me an untouched copy of my repository as it exists on that site right now. Does anyone have contact info for Chisel? The site still has James Turner's name on it. I would very much like for this bug to be fixed. Though --verily looks promising. Donny Ward
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
