,
_create_uv_options = ,
_execute = ,
_pipes_are_closed = ,
_prepare_pipes = ,
_reset = ,
_shutdown = ,
_stop = ,
add_on_exit_callback = ,
after = ,
after_failure = ,
after_success = ,
and_then = ,
and_then_on_failure = ,
and_then_on_failure_wrap = ,
and_then_on_success = ,
and_then_on_success_wrap = ,
and_then_wrap = ,
chain = ,
chain_status = ,
co_wait = ,
is_job = ,
join = ,
new = ,
pid = ,
result = ,
send = ,
shutdown = ,
start = ,
stderr_result = ,
sync = ,
wait =
}
}
stack traceback:
.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:406: in function '_execute'
.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:449: in function 'start'
....local/share/nvim/lazy/plenary.nvim/lua/plenary/curl.lua:313: in function 'post'
...u/.local/share/nvim/lazy/codeium.nvim/lua/codeium/io.lua:440: in function 'post'
.../.local/share/nvim/lazy/codeium.nvim/lua/codeium/api.lua:169: in function 'request'
.../.local/share/nvim/lazy/codeium.nvim/lua/codeium/api.lua:176: in function 'do_heartbeat'
.../.local/share/nvim/lazy/codeium.nvim/lua/codeium/api.lua:311: in function ''
vim/_editor.lua: in function
stack traceback:
[C]: in function 'error'
.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:406: in function '_execute'
.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:449: in function 'start'
....local/share/nvim/lazy/plenary.nvim/lua/plenary/curl.lua:313: in function 'post'
...u/.local/share/nvim/lazy/codeium.nvim/lua/codeium/io.lua:440: in function 'post'
.../.local/share/nvim/lazy/codeium.nvim/lua/codeium/api.lua:169: in function 'request'
.../.local/share/nvim/lazy/codeium.nvim/lua/codeium/api.lua:176: in function 'do_heartbeat'
.../.local/share/nvim/lazy/codeium.nvim/lua/codeium/api.lua:311: in function ''
vim/_editor.lua: in function
I got this problem too, after update the plugin. I guess the curl process may not been killed after finished the request, cause system process been run out.
Error 14时12分34秒 msg_show.lua_error Error executing vim.schedule lua callback: .../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:406: Failed to spawn process: { _additional_on_exit_callbacks = {}, _shutdown_check = <userdata 1>, _stderr_results = {}, _stdout_results = {}, _user_on_exit = <function 1>, args = { "-sSL", "-D", "/tmp/plenary_curl_223c46fc.headers", "-X", "POST", "-H", "Content-Type: application/json", "-d", "@/tmp/lua_xXzsA0", "http://127.0.0.1:64597/exa.language_server_pb.LanguageServerService/Heartbeat" }, command = "curl", enable_handlers = true, enable_recording = true, interactive = true, pid = "EAGAIN: resource temporarily unavailable", stderr = <userdata 2>, stdin = <userdata 3>, stdout = <userdata 4>, user_data = {},
when problem occurs, I found thounds of curl process running like 501 99453 ?? 0:00.02 curl -sSL -D /tmp/plenary_curl_cdd9486f.headers -X POST -H Content-Type: application/json -d @/tmp/lua_IFnUUU http://127.0.0.1:50470/exa.language_server_pb.LanguageServerService/Heartbeat 501 99478 ?? 0:00.05 /usr/bin/curl http://127.0.0.1:50442/exa.language_server_pb.LanguageServerService/Heartbeat --header Content-Type: application/json -d@- 501 99514 ?? 0:00.02 curl -sSL -D /tmp/plenary_curl_33cc4e2c.headers -X POST -H Content-Type: application/json -d @/tmp/lua_fXOsEW http://127.0.0.1:50470/exa.language_server_pb.LanguageServerService/Heartbeat 501 99542 ?? 0:00.06 /usr/bin/curl http://127.0.0.1:50442/exa.language_server_pb.LanguageServerService/Heartbeat --header Content-Type: application/json -d@- 501 99591 ?? 0:00.02 curl -sSL -D /tmp/plenary_curl_71924637.headers -X POST -H Content-Type: application/json -d @/tmp/lua_MJN4IU http://127.0.0.1:50470/exa.language_server_pb.LanguageServerService/Heartbeat 501 99619 ?? 0:00.05 /usr/bin/curl http://127.0.0.1:50442/exa.language_server_pb.LanguageServerService/Heartbeat --header Content-Type: application/json -d@- 501 99662 ?? 0:00.02 curl -sSL -D /tmp/plenary_curl_ec1344e3.headers -X POST -H Content-Type: application/json -d @/tmp/lua_i4ScsR http://127.0.0.1:50470/exa.language_server_pb.LanguageServerService/Heartbeat 501 99699 ?? 0:00.05 /usr/bin/curl http://127.0.0.1:50442/exa.language_server_pb.LanguageServerService/Heartbeat --header Content-Type: application/json -d@- 501 99736 ?? 0:00.02 curl -sSL -D /tmp/plenary_curl_cee547cc.headers -X POST -H Content-Type: application/json -d @/tmp/lua_BIPljd http://127.0.0.1:50470/exa.language_server_pb.LanguageServerService/Heartbeat 501 99763 ?? 0:00.05 /usr/bin/curl http://127.0.0.1:50442/exa.language_server_pb.LanguageServerService/Heartbeat --header Content-Type: application/json -d@- 501 99799 ?? 0:00.02 curl -sSL -D /tmp/plenary_curl_b2f34f24.headers -X POST -H Content-Type: application/json -d @/tmp/lua_6r1XoG http://127.0.0.1:50470/exa.language_server_pb.LanguageServerService/Heartbeat 501 99837 ?? 0:00.05 /usr/bin/curl http://127.0.0.1:50442/exa.language_server_pb.LanguageServerService/Heartbeat --header Content-Type: application/json -d@- 501 99873 ?? 0:00.02 curl -sSL -D /tmp/plenary_curl_31b0407b.headers -X POST -H Content-Type: application/json -d @/tmp/lua_E9F09j http://127.0.0.1:50470/exa.language_server_pb.LanguageServerService/Heartbeat 501 99898 ?? 0:00.05 /usr/bin/curl http://127.0.0.1:50442/exa.language_server_pb.LanguageServerService/Heartbeat --header Content-Type: application/json -d@- 501 99947 ?? 0:00.02 curl -sSL -D /tmp/plenary_curl_fe124712.headers -X POST -H Content-Type: application/json -d @/tmp/lua_dsJlWQ http://127.0.0.1:50470/exa.language_server_pb.LanguageServerService/Heartbeat 501 99975 ?? 0:00.05 /usr/bin/curl http://127.0.0.1:50442/exa.language_server_pb.LanguageServerService/Heartbeat --header Content-Type: application/json -d@-
I got this problem too, after update the plugin. I guess the curl process may not been killed after finished the request, cause system process been run out.