Have no fear...it was shunned! Thanks for the info on individual items. However, I did try this with just lots of smaller items to build up a large repository. I believe it did much the same thing. I will re-test this and get back to the group. If binary objects are checked in should they be indicated in the "binary-glob" repository options? Fossil does seem pretty good about guessing binary data unlike CVS or SVN.
Thanks, Tony --- On Fri, 3/4/11, Richard Hipp <[email protected]> wrote: From: Richard Hipp <[email protected]> Subject: Re: [fossil-users] Clone Error over network To: [email protected] Date: Friday, March 4, 2011, 8:42 AM On Fri, Mar 4, 2011 at 7:05 AM, Anthony Jefferson <[email protected]> wrote: All, Since this is my first post, I would like to say how much I like Fossil. I discovered Fossil about 4 month ago, did some initial testing and recommended it for use on our many small projects. It is now used on 6 different projects. The other day one of our developers accidentally checked in a large zip file of about 160 meg. Ouch. Maybe you should consider shunning that one artifact. http://www.fossil-scm.org/fossil/doc/trunk/www/shunning.wiki When cloning, Fossil builds up a complete HTTP reply in memory then pushes it over the wire. Each artifact has to fit completely within one reply - there is no mechanism to split huge artifacts up into pieces. I'm guessing that the 160 ZIP archive is requiring too much memory somehow. After that the repository could not be cloned successfully over the network. I ran the following scenario as a test using an XP 64 machine with Apache 2 running Fossil as a CGI. I used the latest windows fossil.exe from the downloads. I created a new repository and began filling it with items. I was able to clone this repository successfully till it got to about 325 meg. At that point the client attempting the clone reaches 98.7% complete and up pops the windows dialog saying "fossil.exe has encountered a problem and needs to close". If I work with the repository locally I can still use it and continue to add artifacts. The network clone simply will not complete successfully. I tested an older fossil.exe from Feb. by creating yet another repository and using "fossil.exe server repo.fossil" as the server. The clone does not complete in the this scenario either. Is there something about the networking I am missing? What can I do to help find the problem? Network Cloning is pretty key to our operation. Thanks, Tony Jefferson _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp [email protected] -----Inline Attachment Follows----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
