vscode-code-autocomplete
vscode-code-autocomplete copied to clipboard
Tabnine 2.8.7 binary not downloaded Inside Proxy and tool doesnt work.
I tried to install the tool inside the proxy network and tabnine 2.8.7 is not downloaded and getting a message -saying extension is dead.
I didn't thought about this one and to be honest I forked and worked on this extension to meet some of my needs. You can manually download TabNine binary from official extension repo (here).
Thanks for the response, where should i copy the binary
Download all the binaries it would be easier instead of identifying which arch, platform, etc. you're using and place it inside extension dir. I'm using macOS so it should be here: /Users/svipas/.vscode/extensions/svipas.code-autocomplete-1.1.0/binaries. So simply find where your VS Code extensions are located, open svipas.code-autocomplete (latest version you're using), create dir binaries and place all binaries as it's in official extension repo, structure should be the same.
@sannamalai76 You said you're using proxy network so as far as I understand it blocks network request to download TabNine binary? If so maybe I should update README or add a command which points you to binaries, etc.
Thanks svipas, Yes it will be a good idea to update the read me , there are lot of folks like me want to use inside proxy
I copied the file but it keeps trying to download everytime i open code. is there any settings i need to update after i copy the binary file
Yeah, I know it contains problems with downloading TabNine binary which I will fix. So basically what I'm thinking is:
- Use different path for TabNine binary. This would make easier to place it if auto download fails for e.g. you're using Proxy, etc. And most importantly it wouldn't download TabNine binary if extension is updated, because right now binary is placed inside extension dir.
- Update
READMEwith info how to download binaries manually and where to place them. - If download fails show notification which points to the
READMEof how to download it manually, etc. - If binary already exists in path don't download TabNine again. I'm saving version in VS Code storage, I will need to change logic of the code which checks if TabNine exists.
@sannamalai76 I guess this covers all your problems?
Yes it covers. thank you for doing this.
Yes it covers. thank you for doing this., Please let me know when the next version will be available with the above fix