Hello all,

I've stumbled on an issue where a fossil repository apparently is in a state 
that it can't pull new checkouts from the remote url. It seemed to be working 
during a "fossil all pull", at least I think it was downloading new bytes at 
that time, but then the last checkout locally isn't the last checkout on the 
remote when inspected with fossil ui and fossil status. I've performed a pull 
with version 1.23 windows build and then when I saw the issue, I tried 
upgrading to 1.24 + rebuild it and then pull again to see if that helps 
(hasn't).

Performing a fossil rebuild and then fossil update shows a brief autosync 
session:


                Bytes      Cards  Artifacts     Deltas
Sent:             130          1          0          0
fossil: *** time skew *** server is slow by 34.7 seconds
Received:          78          2          0          0
Total network traffic: 367 bytes sent, 402 bytes received

-------------------------------------------------------------------------------
checkout:     bb5431489fc1f5cd5eca5e8a39b855d4c549d06f 2013-01-14 21:28:08 UTC
tags:         trunk
comment:      Added manifest for modern Windows appearance (user: edwardlblake)
changes:      None. Already up-to-date


In between the new checkout (which isn't being updated to) and the last 
checkout I've added a bunch of binaries in the megabytes range. Cloning to a 
new repository on the same machine from the remote url was no problem by the 
way, it gets the latest checkout, so it's not so bad. The newly cloned repo is 
12,593KB and the affected repository is 7,963KB so it seems the artifacts 
aren't just stored yet inaccessible. Both have 1 leaf, 1 reportfmt, 12 tag in 
fossil sqlite. From fossil sqlite here are the numbers that differ:

           Fresh  Affected
           -----  --------
blob        793    788
delta       340    331
event       39     38
filename    456    449
mlink       774    760
plink       30     29
unclustered 332    327
tagxref     74     72

0 rows in both: attachment, backlink, concealed, orphan, phantom, private, 
shun, unsent

Since its an open source project I can email the affected local repository 
file, remote repository and the originating local repository file containing 
the latest commit if that helps.


Thanks,
Edward Blake

_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to