When starting a run with an attached git repository, I receive the following error message:
Critical error in run 5f31293e9c7d874742f45k3f: org.eclipse.jgit.api.errors.TransportException: Object too large (2,370,212,045 bytes), rejecting the pack. Max object size limit is 2,147,483,639 bytes. at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:255)
Domino uses jgit to manage git repositories attached to projects. Jgit has a pack size limit of 2GB, which generally means the maximum file size for any file in an attached repo is 2GB.
Note, however, this applies to all branches and past commits to the repo. For example, if you commit a 3GB file to your repo, then delete it in a subsequent commit, it's still being tracked in the repo's history.
The offending data should be removed from the repo. While the steps required to do this will depend on the nature of the issue (while it's generally a single large file, that's not always the case), here are some helpful troubleshooting steps:
1. Download the repo and inspect the
.git/objects/packdirectory for packs larger than 2GB.
2. Use the git-sizer tool to evaluate your repo and identify any problematic blobs or commits - https://github.com/github/git-sizer/. In the case below, we can see there's one large file in repo's history even though on the surface it's only 190 MB.
3. The output of the git-sizer should should show you the largest file. Alternatively, you can use some of the techniques described here to find the largest blobs: https://stackoverflow.com/questions/9456550/how-to-find-the-n-largest-files-in-a-git-repository
4. Once you know which files to remove, you can use this git-forget-blob tool (https://github.com/nachoparker/git-forget-blob) to remove the blob from the repo's history. You can find a more detailed walkthrough here - https://ownyourbits.com/2017/01/18/completely-remove-a-file-from-a-git-repository-with-git-forget-blob/