codota/TabNine

Deactivation after editor restart

PhilipTrauner opened this issue · 3 comments

PhilipTrauner commented

First of all: TabNine is awesome, immediately purchased it after using it for 5 minutes.
I have one small problem though: Every time I restart Sublime (3180) I have to enter my license again because TabNine seemingly forgets that it is already activated.

Sublime Console output:

reloading plugin TabNine.TabNine
reloading settings Packages/TabNine/TabNine.sublime-settings
TabNine: starting version 0.4.7
Exception while interacting with TabNine subprocess: [Errno 32] Broken pipe
TabNine: starting version 0.11.2

Displayed warning:

image

With kind regards,
Philip Trauner

zxqfl commented

Sorry about that, this is definitely a bug. Does the displayed console output appear each time you restart Sublime? That would indicate that the TabNine package directory is getting overwritten. This would also explain why you needed to reenter the key, since the key is stored in the package directory.

PhilipTrauner commented

Weirdly enough, I can not reproduce the bug anymore as of today 😅

reloading plugin TabNine.TabNine
plugins loaded
TabNine: starting version 0.11.2

I'm guessing the issue will crop up again when you decide to release the next update (my interpretation of the first Sublime Text console output)

With kind regards,
Philip Trauner

zxqfl commented

Looks like this is because Package Control deletes all existing files in the directory when it does an update. I'll have to push a TabNine update which moves TabNine config and registration keys to the home directory before updating the Sublime client again.

  • 👍1