codota / tabnine-nvim

Tabnine Client for Neovim
https://tabnine.com
362 stars 32 forks source link

[BUG] Tabnine chat pop errors "e/nvim/plugged/tabnine-nvim/lua/tabnine/chat/binary.lua:82: Expected value but found unexpected end of string at character 65537" #151

Closed allan-simon closed 7 months ago

allan-simon commented 8 months ago

Describe the bug When using Tabnine chat if I try in the chat window to ask it to generate code I will see in my neovim terminal

Error executing vim.schedule lua callback: ...re/nvim/plugged/tabnine-nvim/lua/tabnine/chat/binary.lua:82: Expected value but found unexpected end of string at character 65537
stack traceback:
        [C]: in function 'decode'
        ...re/nvim/plugged/tabnine-nvim/lua/tabnine/chat/binary.lua:82: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

To Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior A clear and concise description of what you expected to happen.

Version Info:

Additional context Add any other context about the problem here.

mumahmud commented 8 months ago

I am facing this issue as well. I have noticed this happens anytime chat completes it's generation. This could be after calling :TabnineFix or :TabnineExplain

aarondill commented 8 months ago

we could bandage this by giving a nicer warning when json decoding fails (i've been wanting to do this for a while actually), but the actual problem lies in the chat binaries outputting non-json (which is proprietary code, so someone on the TabNine team has to fix it)

amirbilu commented 8 months ago

@allan-simon is this still happening? can you share a video of the issue? is it with /generate-test-for-code?

amirbilu commented 8 months ago

@mumahmud can you please check if you're able to get tabnine chat working now

amirbilu commented 7 months ago

closing this as fixed. feel free to re-open.

jsco2t commented 7 months ago

Can we get this re-opened.

I just setup chat today and this issue reproduces fairly consistently for me when using /explain-code