:Rocks sync fails on a new machine

[eldar]

Hi! I created a minimal rocks.nvim configuration and transferred it to a new machine. After running :Rocks sync I am getting the following error message:

emote/host: generated rplugin manifest: /home/eldar/.local/share/rocks/rplugin.vim                                                                                                                                  
Error executing vim.schedule lua callback: ...dar/.local/share/rocks/rocks/share/lua/5.1/nio/tasks.lua:100: Async task failed without callback: The coroutine failed with this message:                              
...r/.local/share/rocks/rocks/share/lua/5.1/nio/control.lua:293: ...e/rocks/rocks/rocks_rtp/lua/rocks/operations/helpers.lua:329: Vim:E151: No match: /usr/share/vim/site/doc/**                                     
stack traceback:                                                                                                                                                                                                     
        [C]: in function 'error'                                                                                                                                                                                     
        ...r/.local/share/rocks/rocks/share/lua/5.1/nio/control.lua:293: in function 'with'                                                                                                                          
        ...hare/rocks/rocks/rocks_rtp/lua/rocks/operations/sync.lua:38: in function <...hare/rocks/rocks/rocks_rtp/lua/rocks/operations/sync.lua:37>                                                                 
stack traceback:                                                                                                                                                                                                     
        [C]: in function 'error'                                                                                                                                                                                     
        ...dar/.local/share/rocks/rocks/share/lua/5.1/nio/tasks.lua:100: in function 'close_task'                                                                                                                    
        ...dar/.local/share/rocks/rocks/share/lua/5.1/nio/tasks.lua:122: in function 'cb'                                                                                                                            
        ...dar/.local/share/rocks/rocks/share/lua/5.1/nio/tasks.lua:188: in function <...dar/.local/share/rocks/rocks/share/lua/5.1/nio/tasks.lua:187>                                                               

Here is the output of :checkhealth

rocks: require("rocks.health").check()

Checking external dependencies ~
- OK luarocks: found /home/eldar/.local/share/rocks/rocks/bin/luarocks 3.11.0
- OK lua: found Lua 5.1.5  Copyright (C) 1994-2012 Lua.org, PUC-Rio

Checking rocks.nvim config ~
- OK No errors found in config.

Checking rocks.toml ~
- OK No errors found in rocks.toml.

Checking tree-sitter parsers ~
- OK No tree-sitter issues detected.

It seems that it manages to install the packages despite this error message, but I would still like to get rid of it. I'm running Neovim 0.10.1 on OpenSUSE Tumbleweed with lua 5.1 installed together with its development packages. Thanks!

[mrcjkb]

Hey 👋

does the error occur after restarting rocks.nvim and after every sync?

It appears to be thrown when rocks.nvim invokes the command :helptags ALL to generate plugins' help pages (which you can try to run manually, with or without rocks.nvim).

I don't know why it's throwing that error (looks like a Neovim issue), but you could work around it by adding the option generate_help_pages = false to your vim.g.rocks_nvim config.
However, this means you would have to invoke :helptags ALL manually to update your plugins' help pages.

[mrcjkb]

That seems to be what's causing the issue.
I don't think it's caused by rocks.nvim. You could verify this by running :helptags ALL with neither rocks.nvim nor lazy.nvim installed.

Which Linux distribution and which package manager are you using?

[eldar]

I deleted ~/.local/share/$NVIM_APPNAME and reinstalled all plugins from scratch and now I don't have this issue anymore! I guess we can consider it closed. Thanks for all the help!

What I also found is that when first starting nvim with an existing config on a new machine, it throws an error when the config tries to use the plugins that haven't been installed yet, so this requires running :Rocks sync manually and a restart. It would be nice to automate it.

[eldar]

you could verify this by running :helptags ALL with neither rocks.nvim nor lazy.nvim installed.

This worked when running nvim without any config. I think my ~/.local/share/$NVIM_APPNAME folder wound up in a bad state after I was trying to get rocks.nvim to work - but starting from the clean slate did the job.

[mrcjkb]

It would be nice to automate it.

it's on our roadmap

[eldar]

Awesome, thanks again for your great work.