Closed sersorrel closed 3 years ago
I'm seeing the same thing with TabNine v2.0.7, in VSCode Insiders v1.38.0 and Atom Nightly v1.42.0. The extension itself seems to be working---TabNine::config
summons a browser with its settings---but the UI hangs at "Establishing connection to TabNine cloud."
My guess is it's throwing a tantrum over a self-signed SSL certificate: I see this in the extension logs...
[2019-08-12][04:19:27][lsp::low_level_language_server][INFO] Calling LSP method `DidChangeTextDocument`
[2019-08-12][04:19:27][lsp::low_level_language_server][INFO] Calling LSP method `Completion`
[2019-08-12][04:19:28][server][DEBUG] [autocomplete] 54 ms
[2019-08-12][04:19:28][server][DEBUG] [autocomplete] 1 ms
[2019-08-12][04:19:28][server][DEBUG] [autocomplete] 1 ms
[2019-08-12][04:19:28][server][DEBUG] [autocomplete] 1 ms
[2019-08-12][04:19:28][server][DEBUG] [autocomplete] 0 ms
[2019-08-12][04:19:29][server][DEBUG] [autocomplete] 0 ms
[2019-08-12][04:19:29][ui::http_server][INFO] Started config server at V4(127.0.0.1:5555).
[2019-08-12][04:19:29][server][DEBUG] [autocomplete] 71 ms
[2019-08-12][04:19:29][lunar_transport::controller][INFO] Connecting to V4(35.226.242.34:7777)
[2019-08-12][04:19:30][lunar_transport::controller][ERROR] Error establishing SSL connection: The certificate was not trusted.
...and OpenSSL chokes on 35.226.242.34:7777
as well. Turning off the Cloud restored the basic functionality.
Repro steps:
What did you expect to happen?
TabNine Cloud should work in newly-created, not-yet-written files, as well as existing files.
What actually happened?
TabNine doesn't appear to connect to TabNine Cloud when editing a new file.