Potential Git Issues with Project

[Calem Bendell]

This is an issue I've never come across before, but I get "early eof and index pack failed" errors when cloning the touchram repository in Windows.

I fixed this by doing a git clone with a depth of one and then fetching again with a deep fetch ("unshallow"), suggested by StackOverflow. If you need to do this, you sometimes need to reset your remote.origin.fetch in your git config, which I have done.

I'm not sure if I've now correctly downloaded the entire repository, but my disk has about 300MB for TouchRAM, most of which is either revisions or binaries (well... bytecodes). Other very large files in the repository include mt4j.jar, reflections uberjar, and guava, but for the most part the current source including libraries seems to be about 4-6% of the repository. It may be worth considering squashing the git history and identifying where these space penalties are being incurred.

Another option is to make touchram a legacy repository and begin a new touchcore repository?

[Calem Bendell]

Further research suggests this may be a bitbucket server memory limit.

I haven't been able to find the bitbucket memory limit for a single clone instance, though.

[Matthias Schoettle]

Which client do you use to clone the repository? Have you tried a different one?

Maybe try the .gitconfig settings or the new line changes as mentioned in the comments here: https://stackoverflow.com/questions/1943914/git-clone-fails-with-index-pack-failed

[Calem Bendell]

I've found a few workarounds.

If using the command line client, the shallow clone then unshallow fetch seems to work fairly well.

Best is switching the end of line type.

[Matthias Schoettle]

Sweet!