bug(plenary.nvim): Section bug
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Lua
- Estrellas
- 3.5k
- Forks
- 340
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nvim-lua/plenary.nvim
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
nvim-lua/plenary.nvim#682 ·
-
uniform usage of `os.getenv`Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
nvim-lua/plenary.nvim#680 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
nvim-lua/plenary.nvim#675 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 28/100
nvim-lua/plenary.nvim#672 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
nvim-lua/plenary.nvim#671 · 1 comentario ·
Todos los issues de nvim-lua/plenary.nvim
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
JohnnyMorganz/luau-lsp#1635 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
mapper bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
-
Zenmap CrashAbiertoZenmap
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 2 días