jdhao / nvim-config

A modern Neovim configuration with full battery for Python, Lua, C++, Markdown, LaTeX, and more...
MIT License
3.53k stars 524 forks source link

Issue with gitsigns package #343

Open hhammoud01 opened 1 week ago

hhammoud01 commented 1 week ago

Describe the bug

Error executing vim.schedule lua callback: ...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:105: The coroutine failed with this message: ...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:180: attempt to call upvalue ' func' (a number value) stack traceback: ...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua: in function 'attach' ...im/site/pack/packer/start/gitsigns.nvim/lua/gitsigns.lua:132: in function 'setup_attach' ...im/site/pack/packer/start/gitsigns.nvim/lua/gitsigns.lua:191: in function <...im/site/pack/packer/start/gitsigns.nvim/lua/gitsigns.lua:167> stack traceback: [C]: in function 'error' ...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:105: in function 'cb' ...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:140: in function <...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:139>

It seems that there is an issue with gitsigns package. The error appears "only occasionally" (every 5-6 times I open nvim). After pressing any key when I get the error, It disappears.

Steps to reproduce the issue:

  1. Open nvim every 4-5 times.

Expected behavior Not getting the error on start.

Screenshots image

jdhao commented 1 week ago

I haven't seen this issue myself. Maybe it is related to your environment. Please report to gitsigns instead.