Error executing Lua callback: ...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:29: The coroutine failed with this message: ...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:108: assertion failed!
stack traceback:
[C]: in function 'assert'
...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:108: in function 'do_clean'
...data\site\pack\pckr\start\pckr.nvim/lua/pckr/actions.lua:416: in function <...data\site\pack\pckr\start\pckr.nvim/lua/pckr/actions.lua:415>
stack traceback:
[C]: in function 'error'
...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:29: in function 'step'
...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:52: in function 'run'
...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:110: in function 'cmd_func'
...vim-data\site\pack\pckr\start\pckr.nvim/lua/pckr/cli.lua:89: in function <...vim-data\site\pack\pckr\start\pckr.nvim/lua/pckr/cli.lua:74>
Pckr sync log:
Error executing Lua callback: ...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:29: The coroutine failed with this message: ...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:108: assertion failed!
stack traceback:
[C]: in function 'assert'
...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:108: in function 'do_clean'
...data\site\pack\pckr\start\pckr.nvim/lua/pckr/actions.lua:332: in function 'sync'
...data\site\pack\pckr\start\pckr.nvim/lua/pckr/actions.lua:396: in function <...data\site\pack\pckr\start\pckr.nvim/lua/pckr/actions.lua:395>
stack traceback:
[C]: in function 'error'
...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:29: in function 'step'
...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:52: in function 'run'
...m-data\site\pack\pckr\start\pckr.nvim/lua/pckr/async.lua:110: in function 'cmd_func'
...vim-data\site\pack\pckr\start\pckr.nvim/lua/pckr/cli.lua:89: in function <...vim-data\site\pack\pckr\start\pckr.nvim/lua/pckr/cli.lua:74>
Expected behaviour
Commands clean and sync work as expected.
Aside: It could be nice to have :Pckr upgrade print the version number/git hash in the window title, or add it somewhere in the helpfiles. Before creating this issue I tried finding a version number for Pckr to add to the report but had no luck. I could find where the git repo is cloned in my Windows userdata somewhere but that extra friction is not optimal.
nvim --version
:git --version
:git version 2.46.0.windows.1
Windows 11 Home 23H2
alacritty 0.13.2 (bb8ea18)
Steps to reproduce
nvim -u NORC
:Pckr clean
OR:Pckr sync
Actual behaviour
Pckr clean log:
Pckr sync log:
Expected behaviour
Commands
clean
andsync
work as expected.Aside: It could be nice to have
:Pckr upgrade
print the version number/git hash in the window title, or add it somewhere in the helpfiles. Before creating this issue I tried finding a version number for Pckr to add to the report but had no luck. I could find where the git repo is cloned in my Windows userdata somewhere but that extra friction is not optimal.