search

Exafunction / codeium.nvim

A native neovim extension for Codeium
MIT License
658 stars 50 forks source link

[bug] request error #8

Closed towry closed 1 year ago

towry commented 1 year ago 
completion request failed                                                                  
│completion request failed                                                                  
│[codeium] [ERROR 09:17:24] ...ocal/share/nvim/lazy/codeium.nvim/lua/codeium/notify.lua:14: 
│completion request failed:  {                                                              
│[codeium]   code = 0,                                                                      
│[codeium]   out = '{"code":"canceled","message":"Post \\"https://server.codeium.com:443/exa
│.api_server_pb.ApiServerService/GetCompletions\\": context canceled"}',                    
│[codeium]   response = {                                                                   
│[codeium]     body = '{"code":"canceled","message":"Post \\"https://server.codeium.com:443/
│exa.api_server_pb.ApiServerService/GetCompletions\\": context canceled"}',                 
│[codeium]     exit = 0,                                                                    
│[codeium]     headers = { "Accept-Encoding: gzip", "Content-Type: application/json", "Vary:
│ Origin", "Date: Mon, 30 Jan 2023 01:17:23 GMT", "Content-Length: 139", "", "" },          
│[codeium]     status = 408                                                                 
│[codeium]   },                                                                             
│[codeium]   status = 408                                                                   
│[codeium] }

This error seems like an api call debounce related error.

jcdickinson commented 1 year ago

Does the plugin work at all, i.e. would it make sense to silence these cancellations?

It should be pretty difficult to run into debounce, as cmp already debounces to a certain degree.

towry commented 1 year ago

Does the plugin work at all, i.e. would it make sense to silence these cancellations?

Silence these cancellations maybe is a workaround. This plugin works with this error.