-
Notifications
You must be signed in to change notification settings - Fork 503
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
Log to find semantic problem #136
Comments
I have the same problem, but with Typescript.
|
I'm using nvm and have the same issue if that gives any clues. I have followed the instructions on tabnine.com/semantic but it did not help. |
Try to append ".cmd" to the command in TabNine.toml as suggested here: codota/tabnine-vscode#45 Had the same issues, and this fixed it for me as well. |
I tried appending ".cmd" but that did not resolve my issue. Even after running TabNine::restart, it still gives the error code. |
@Cy-Tek it worked for me |
@Cy-Tek Are you sure you edit |
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. |
Thanks for amazing extension. I found a problem with enabling semantic autocomplete.
TabNine can’t start
flow
binary, but I install it to the system and it is available byflow lsp
command in terminal. It could be the problem of my environment (for instance, Flatpak container restrictions).But I need some debug information to fix it. Where I can find TabNine log?
The text was updated successfully, but these errors were encountered: