Open smacintyre opened 2 years ago
You can use Open in vscode
option in Gitpod and maybe you will be able to login then but I guess that's not what you want since you will have to use VSCODE locally then.
@axonasif Running local completely defeats the point and value of gitpod. It should work in gitpod directly.
@smacintyre This is because Tabnine server behaves like this. Can't resolve it, but we can temp resolve it
Sign in with Tabnine to xxx
port 5555 will start listening127.0.0.1:5555/xxxxx
to auth back$ curl -L <tabnine_auth_back_url>
in browser code terminal to get our auth info~3. Open port in browser code like image below, copy its URL like https://5555-gitpodio-templatetypescr-hpp3558c4lo.ws-us38.gitpod.io/home
~
~4. Paste https://5555-gitpodio-templatetypescr-hpp3558c4lo.ws-us38.gitpod.io
to all tab redirect to 127.0.0.1:5555
in step2 (I do this twice~
Then we got Tabnine login succeed
~Open Port~ | Succeed |
---|---|
![]() |
![]() |
~Can we hook hosts like 127.0.0.1
localhost
in simple browser service worker, so that users can simply paste auth back URL to login?~
Not correct behavior
cc @jeanp413
Maybe we can file an issue to Tabnine, to ask if they want to use polling instead of auth back. Because it does not work in code browser (Github Codespaces included)
cc @jeanp413 @smacintyre
@mustard-mh Since, as per the blog post, Gitpod is partnered with Tabnine, I assume you have channels for escalating this. I mean, it's within both company's interest to have Tabnine working in Gitpod. The customer base overlaps.
Thank you for looking into this.
@smacintyre I see, we can run curl -L <tabnine_auth_back_url>
in browser code to auth back, it's a simple temp solution for now 😄
Gitpod is partnered with Tabnine, I assume you have channels for escalating this.
I'll ask if we are and we have 🙏
@mustard-mh Since, as per the blog post, Gitpod is partnered with Tabnine, I assume you have channels for escalating this. I mean, it's within both company's interest to have Tabnine working in Gitpod. The customer base overlaps.
We appreciate your patience, @smacintyre, we're speaking with the Tabnine folks now to try and resolve.
Relates to:
So, some changes were added by @dimacodota https://github.com/codota/tabnine-vscode/pull/801 to try and address the issue, however I still have issues with the sidebar not authenticating properly still.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is your feature request related to a problem? Please describe
Last year GitPod claimed that TabNine would work with Gitpod. However, it still doesn't. I cannot authenticate and use the pro features I'm paying for.
If I try to login, I get redirect to 127.0.0.1:5555:
It's really frustrating that this was announced 6 months ago but tabnine still isn't supported.
Describe the behaviour you'd like
I can authenticate so I can my Tabnine features.