Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

bug(plenary.nvim): Section bug

未关闭
#658 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
lua
领域
tooling

调研方向

Start by reproducing the gd failure in the neogit diff popup, then trace the nil section access in neogit/lua/neogit/popups/diff/init.lua through neogit/process.lua and plenary/lua/plenary/async/async.lua. Determine whether the incompatibility belongs to plenary or neogit, and confirm the diff popup no longer raises the reported error.

由索引模型根据 Issue 内容生成。

描述

Error Message:

...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:18: The coroutine failed with this message: ...l/share/nvim/lazy/neogit/lua/neogit/popups/diff/init.lua:9: attempt to index field 'section' (a nil value)
stack traceback:
	[C]: in function 'error'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:18: in function 'callback_or_next'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:45: in function 'step'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:48: in function 'execute'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:118: in function 'callback'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:25: in function 'callback_or_next'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:45: in function 'saved_callback'
	...are/nvim/lazy/plenary.nvim/lua/plenary/async/control.lua:126: in function 'tx'
	.../share/nvim/lazy/plenary.nvim/lua/plenary/async/util.lua:71: in function 'callback'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:25: in function 'callback_or_next'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:45: in function 'cb'
	...rne/.local/share/nvim/lazy/neogit/lua/neogit/process.lua:361: in function <...rne/.local/share/nvim/lazy/neogit/lua/neogit/process.lua:315> function: builtin#18 ...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:18: The coroutine failed with this message: ...l/share/nvim/lazy/neogit/lua/neogit/popups/diff/init.lua:9: attempt to index field 'section' (a nil value)
stack traceback:
	[C]: in function 'error'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:18: in function 'callback_or_next'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:45: in function 'step'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:48: in function 'execute'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:118: in function 'callback'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:25: in function 'callback_or_next'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:45: in function 'saved_callback'
	...are/nvim/lazy/plenary.nvim/lua/plenary/async/control.lua:126: in function 'tx'
	.../share/nvim/lazy/plenary.nvim/lua/plenary/async/util.lua:71: in function 'callback'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:25: in function 'callback_or_next'
	...share/nvim/lazy/plenary.nvim/lua/plenary/async/async.lua:45: in function 'cb'
	...rne/.local/share/nvim/lazy/neogit/lua/neogit/process.lua:361: in function <...rne/.local/share/nvim/lazy/neogit/lua/neogit/process.lua:315>

How the error occured:
I was using the neogit plugin, and used the keybind 'gd' which should've opened the difference popup specific to that plugin, it's meant to mimick that functionality of the git command 'git diff'. Just to give context.

Thoughts:
I'm unsure whether this is a Neovim v0.11.1 issue, but I've never seen this issue before, and I believe it to be a compatibility issue with the aforementioned plugin.

Why place issue here and not on the 'neogit.nvim' repo?:
I don't know really to be completely honest. When looking at the paths displayed within the error, they point to plenary.nvim, not anything got to do with the neogit plugin. Or could possibly be due to an update with plenary that neogit itself must cater for instead.

主要语言
Lua
星标
3.5k
派生
341
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nvim-lua/plenary.nvim 的其他 Issue

查看 nvim-lua/plenary.nvim 的全部 Issue

相似的 Issue

更多 Lua Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。