DEV2-3247 - Fix: Startup Issue in devcontainers

[mikekosulin]

Extension was failing to initialize correctly when launched in devcontainers. Upon investigating, it appears that users needed to manually input certain settings to workaround this issue.

To enable the Tabnine extension to work with devcontainers, users have been required to add the following settings to their VSCode settings.json:

// VSCode user's settings.json
{
  "remote.extensionKind": {
    "TabNine.tabnine-vscode": [
      "ui",
      "workspace"
    ]
  }
}

Considering the complexity and inconvenience this imposes on users, I've prepared this PR to address and resolve the issue.

[dimacodota]

hey @mikekosulin, is there any specific reason for choosing this order and not ["workspace", "ui"]?

[mikekosulin]

Yeah, I’ve checked a few options and ["workspace", "ui"] doesn’t affect on the issue. So Tabnine extension activates if setting is ["ui", "workspace"] or ["ui"]

You can easily check it by following these steps to reproduce:

1. Start any devcontainer
2. Install Tabnine extension
3. Add the the code below to your settings and reload the VS Code window:

// VSCode user's settings.json
{
  "remote.extensionKind": {
    "TabNine.tabnine-vscode": [
      "workspace",
      "ui"
    ]
  }
}

Also in my opinion, #534 would be beneficial to merge.

[dimacodota]

LGTM

[amircodota]

@mikekosulin

Hi, Mike

I am afraid we have to revert this PR.

It causes issues to many users working via remote ssh and other remote options.

I think we need to come up with a different solution for devcontainers - one that allows tabnine to run inside the container.

We will be looking into this and would love your input. So feel free to open an issue or contact our support and describe your situation in more detail