Thus said Donny Ward on Sat, 21 Jun 2014 17:29:07 -0700: > I have two versions of my repository that I've saved from a while ago, > the last time I ran into this syncing issue. I've linked them both > here, hoping that someone can analyze them and figure out what the > issue is.
Indeed it doesn't pull from the other file either: $ fossil pull wilderness-chiselapp.fossil -R wilderness-local.fossil Round-trips: 1 Artifacts sent: 0 received: 0 Pull finished with 268 bytes sent, 1348 bytes received If I add --verily, I get a lot more than just the missing artifact that you pointed out (a9b1344817). $ fossil pull --verily wilderness-chiselapp.fossil -R wilderness-local.fossil Round-trips: 4 Artifacts sent: 0 received: 626 Pull finished with 18384 bytes sent, 1870627 bytes received It looks like --verily causes the server to respond with an igot for every artifact that it knows about, which explains why these missing artifacts get detected by the client which will send gimme requests for each missing artifact to be transferred. Why doesn't the client know that it needs to send gimme for these missing artifacts? I've been looking at the following to try to understand from a high level what might be happening: http://www.fossil-scm.org/index.html/doc/trunk/www/sync.wiki I wonder if perhaps a9b1344817 is not mentioned in any cluster artifacts and it is not being published in the unclustered table? Or, is it possible that the artifact was added to a cluster that it had previously already received so it doesn't request it? (Be aware that I'm speculating at this point because I don't yet know how clusters work.) Will definitely require further investigation. By the way, if you want to see what the other 625 missing artifacts were, run: fossil pull --verily --httptrace wilderness-chiselapp.fossil -R wilderness-local.fossil Then look at the http-* files that appear: $ grep gimme http-request-* | random 100 http-request-2.txt:gimme 3621fa11299ea8ab263e754cec37690d4581f660 http-request-3.txt:gimme acf4a8977ca5fc2a11bec925b38189e033da5a3f http-request-3.txt:gimme c100340071c21bf707fb0f6db59fef793ef3d02a http-request-4.txt:gimme dee041c7e5eaed008132257b22951166b1a6debc http-request-4.txt:gimme e983a75954eace1dc404cdd6d554947cb8a1fc41 It looks like at least this random selection are all files that were part of checkin a9b1344817, perhaps all of them are. Andy -- TAI64 timestamp: 4000000053a679b8 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
