Help: Error curl.lua:300

Open
#609 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
lua, neovim
Domain
tooling

Research direction

Start by reviewing plenary.nvim/lua/plenary/curl.lua around line 300 and plenary.nvim/lua/plenary/job.lua around line 241, then reproduce the reported callback failure with Neovim v0.10.0 on Void Linux. Compare the curl error and stack trace with the request's output-handling path; done requires identifying a reproducible cause and confirming an appropriate fix or explanation.

Written by the indexing model from the issue text.

Description

Error executing luv callback:
....local/share/nvim/lazy/plenary.nvim/lua/plenary/curl.lua:300: post http://127.0.0.1:32899/exa.language_server_pb.LanguageServerService/Heartbeat - curl error ex
it_code=23 stderr={ "curl: (23) Failed writing received data to disk/application" }
stack traceback:
[C]: in function 'error'
....local/share/nvim/lazy/plenary.nvim/lua/plenary/curl.lua:300: in function '_user_on_exit'
.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:241: in function '_shutdown'
.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:48: in function <.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:39>

Version: NVIM v0.10.0
0S: Void Linux

Dominant language
Lua
Stars
3.5k
Forks
340
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nvim-lua/plenary.nvim

All issues in nvim-lua/plenary.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.