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

Tabnine code suggestion and filename issue #1547

Open
AP-Sig opened this issue Jan 12, 2025 · 1 comment
Open

Tabnine code suggestion and filename issue #1547

AP-Sig opened this issue Jan 12, 2025 · 1 comment

Comments

@AP-Sig
Copy link

AP-Sig commented Jan 12, 2025

please complete the following information:

  • OS version: Windows 11
  • Editor version VSCodium 1.96.2
  • Programming language: Python
  • TabNine extension version: 3.220.0
  • Model: Claude 3.5 Sonnet

{78AC8D42-E9AC-4CB6-9715-5329B0773D73}

Issue Details:

I recently (a couple days ago) started having a minor issue with how Tabnine references code suggestions in it's output for the VSCode extension. Before, it would reference the file directly in the suggestion and clicking "Apply" would correctly apply the code changes in the active file I'm working with. However, currently any suggested changes are referencing a file "VS" that does not exist in the workspace. This file is located at "C:/Users/MyUsername/Documents/VS". I'm attaching a screenshot of this issue in an example prompt:

{5279D4E2-D11D-427F-85D5-2A14D8C23790}

I should mention that this is happening with the Claude 3.5 Sonnet model, and this is not the case with the Tabnine Protected model.

Again, where it has </> VS it should have the filename of the file I'm working in. No changes have been made to the workspace or any other VSCodium settings. This issue began seemingly at random.

gz#38112

(related to Zendesk ticket #38112)

@AP-Sig AP-Sig changed the title Tabnine code suggestions Tabnine code suggestion and filename issue Jan 12, 2025
@amirbilu
Copy link
Contributor

@AP-Sig we recently made changes around this logic. Is it working better for you now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants