Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with gitsigns package #343

Open
hhammoud01 opened this issue Oct 18, 2024 · 1 comment
Open

Issue with gitsigns package #343

hhammoud01 opened this issue Oct 18, 2024 · 1 comment

Comments

@hhammoud01
Copy link

  • nvim --version: NVIM v0.10.2 / Build type: Release / LuaJIT 2.1.1727870382.
  • terminal emulator and version: Iterm 2 build 3.5.5
  • Operating system/version: MacOS Version 13.0.1 (22A400) (VENTURA)
  • Have you read and followed all steps in the doc: Yes
  • Output of command set runtimepath: None

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
Copy link
Owner

jdhao commented Oct 18, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants