-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
You can use |
@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
Then we got Tabnine login succeed
|
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) |
@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
I'll ask if we are and we have 🙏 |
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 codota/tabnine-vscode#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.
The text was updated successfully, but these errors were encountered: