Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Issue - command Tabnine.saveSnippet not found
See original GitHub issueIssue Description
please complete the following information:
- OS version: Win 10,
- Editor version VSCode 1.67.2:
- Programming language: ts
- TabNine extension version: 3.5.53
- Licence: Free
Issue Details:
While running Tabnine: Save Snippet i receive and error command Tabnine.saveSnippet not found. Is it normal?
gz#14659
Issue Analytics
- State:
- Created 9 months ago
- Reactions:4
- Comments:5
Top Results From Across the Web
Tabnine is not running
Tabnine is not starting, not offering suggestions, not responding to commands such as tabnine::config, etc.
Read more >Tabnine autocomplete AI stopped working in Visual Studio ...
I installed Tabnine autocomplete not long ago (around 2 hours) in visual studio via the Extensions ( Ctrl + Shift + X )....
Read more >Tabnine not working on wsl? Is this something i can fix or is it ...
Is this something i can fix or is it a thing from tabnine's side ... i get this error when i open files...
Read more >Tabnine AI Autocomplete for Javascript, Python, Typescript ...
Launch VS Code Quick Open ( Ctrl+P ), paste the following command, ... Tabnine does not retain any user code beyond the immediate...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks @skoniks! I passed the config on and talked to our devs about it. I was told that this is about to be removed from the extension and is no longer supported. So that is why you both encountered this message.
I have same error. Who knows what is it?