Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support using Tabnine with Gitpod #8776

Open
smacintyre opened this issue Mar 13, 2022 · 10 comments
Open

Support using Tabnine with Gitpod #8776

smacintyre opened this issue Mar 13, 2022 · 10 comments
Assignees
Labels
editor: code (browser) meta: never-stale This issue can never become stale team: IDE type: bug Something isn't working

Comments

@smacintyre
Copy link

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.

image

If I try to login, I get redirect to 127.0.0.1:5555:
image

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.

@axonasif
Copy link
Member

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 axonasif added the type: bug Something isn't working label Mar 13, 2022
@smacintyre
Copy link
Author

@axonasif Running local completely defeats the point and value of gitpod. It should work in gitpod directly.

@mustard-mh
Copy link
Contributor

mustard-mh commented Mar 22, 2022

@smacintyre This is because Tabnine server behaves like this. Can't resolve it, but we can temp resolve it

  1. click Sign in with Tabnine to xxx port 5555 will start listening
  2. Tabnine will open a tab link to 127.0.0.1:5555/xxxxx to auth back
  3. Run $ 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
image image

@mustard-mh
Copy link
Contributor

mustard-mh commented Mar 22, 2022

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

@mustard-mh
Copy link
Contributor

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

@smacintyre
Copy link
Author

@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.

@mustard-mh
Copy link
Contributor

mustard-mh commented Mar 22, 2022

@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 🙏

@loujaybee
Copy link
Member

loujaybee commented Mar 31, 2022

@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:

@loujaybee
Copy link
Member

loujaybee commented Apr 11, 2022

So, some changes were added by @dimacodota codota/tabnine-vscode#801 to try and address the issue, however I still have issues with the sidebar not authenticating properly still.

@stale
Copy link

stale bot commented Jul 10, 2022

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Jul 10, 2022
@loujaybee loujaybee added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editor: code (browser) meta: never-stale This issue can never become stale team: IDE type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants