Thus said Andy Gibbs on Wed, 02 Dec 2015 16:56:35 +0100: > I can certainly let you know when (if?) it happens again. What can I > say about my usage patterns? ... I am certainly doing large check-ins, > for example, modifying 100s of files at once.
That certainly is similar to the criteria for the previous conditions. Before the previous fix I had reproduced it with 1,500 changed files in a single commit, thus resulting in a manifest with a lot of F-cards. I saw in the referenced threads that max-download also had something to do with it: http://marc.info/?l=fossil-users&m=144565833040818&w=2 Though I'm not sure that is actually a requirement for reproducing the problem. At any rate, I had default values for max-download. One thing you can do on the server is run: fossil test-clusters /path/to/project.fossil Andy -- TAI64 timestamp: 40000000565fc353 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
