You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
please complete the following information:
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:
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)
The text was updated successfully, but these errors were encountered: