TabNine extension version(Type TabNine::version in insert mode): 3.7.25
If the issue is related to TabNine failure, please provide log files:
Type TabNine::config in your editor, the logs are located at the bottom of the page.
Issue Details:
In this repo, we add binaries for Tabnine Engines into Git histories. This makes the Git repo extremely large and takes too long to install or upgrade. The .git folder grows as we update the binary files.
In the screenshot below:
It takes 198 seconds to get a full clone (requires 1018M disk space) or 53 seconds to get a fresh shallow clone (requires 506M disk space). Using vim-plug, sometimes, it takes more than 5 minutes to upgrade Tabnine on a shallow clone.
I think we should provide a separate method to install the binaries rather than put the binaries to Git histories.
please complete the following information:
vim --version
): vim 8.2TabNine extension version(Type
TabNine::version
in insert mode): 3.7.25If the issue is related to TabNine failure, please provide log files:
Type
TabNine::config
in your editor, the logs are located at the bottom of the page.Issue Details:
In this repo, we add binaries for Tabnine Engines into Git histories. This makes the Git repo extremely large and takes too long to install or upgrade. The
.git
folder grows as we update the binary files.In the screenshot below:
It takes 198 seconds to get a full clone (requires 1018M disk space) or 53 seconds to get a fresh shallow clone (requires 506M disk space). Using
vim-plug
, sometimes, it takes more than 5 minutes to upgrade Tabnine on a shallow clone.I think we should provide a separate method to install the binaries rather than put the binaries to Git histories.