How to silence message about deprecated rocks.packadd?

[salkin-mada]

Hi team! My neovim life has been going thru Plug, Packer and Lazy. I have been using Rocks for 48 hours now, and it is so so so sweet. Rocks.nvim = QOL
But one thing is interfering, almost intruding :-)
I am constantly getting the following message when I start up neovim. And sometimes also when adding new buffers.

rocks.packadd is deprecated, use Neovim's built-in 'packadd' instead.                                                             
Feature will be removed in rocks.nvim 3.0.0   

How can this be silenced?

[mrcjkb]

Hey 👋

Thanks for the nice words 😄
We recently made rocks.nvim compatible with neovim's built-in :packadd and deprecated :Rocks packadd and require("rocks").packadd (#292).

Are you calling one of those in your config somewhere?

[salkin-mada]

@mrcjkb for some esoteric (but logical, HUMAN it was probably something you did) reason.
I have not been able to reproduce this since adding error("deprecated") hah!
Sorry.. :-)
I will come back to this discussion if the deprecation message suddenly appears again - without any obviously reason why.

[salkin-mada]

You wont believe it. I dont .. I can reproduce 10-25% of the time again now.
nvim then :Rocks edit (treesitter getting toml parser, nevertheless auto_install = false) as soon as it is done, boom throws:

rocks.packadd is deprecated, use Neovim's built-in 'packadd' instead.                                                             
Feature will be removed in rocks.nvim 3.0.0

But! if I change rocks.nvim init.lua as suggested:

---@deprecated
function rocks.packadd(rock_name, opts)
	error("ding ding dong deprecated")
    vim.deprecate("rocks.packadd", "Neovim's built-in 'packadd'", "3.0.0", "rocks.nvim")
    require("rocks.runtime").packadd(rock_name, opts)
end

and then nvim then :Rocks edit (treesitter is now silent, like expected.. auto_install=false).
yes.. no deprecation message.

Okay I go back and comment out error("ding ding dong deprecated"). And we are back to:
nvim then :Rocks edit (treesitter getting toml parser, nevertheless auto_install = false) as soon as it is done, boom throws:

rocks.packadd is deprecated, use Neovim's built-in 'packadd' instead.                                                             
Feature will be removed in rocks.nvim 3.0.0

And I kept doing this back and forth. Was actually able to make it post the deprecation message with the error("ding ding dong deprecated") added to the rocks init.lua file. And the error message was no where to be found in my mess. So the problem is not rocks init.
...
Soo this makes no sense and is super esoteric.
I then just started doing nvim and then :Rocks edit. Here is a film so you can see how erratic it is:

huhuhu.mov

Notice that its only sometimes rocks-treesitter runs on startup. And its only sometimes it throws the deprecation mess..
But all the time its very aggressively installing the parser of given (buffer) filetype -> just by switch focus away from the terminal window and then back again.? crazy huh?

In the end I managed to "provoke" this error:

rocks.packadd is deprecated, use Neovim's built-in 'packadd' instead.                                                                       
Feature will be removed in rocks.nvim 3.0.0                                                                                                 
stack traceback:                                                                                                                            
        ...kin/.local/share/nvim/rocks/rocks_rtp/lua/rocks/init.lua:14: in function 'packadd'                                               
        ....local/share/nvim/rocks/share/lua/5.1/rocks/commands.lua:225: in function 'impl'                                                 
        ....local/share/nvim/rocks/share/lua/5.1/rocks/commands.lua:244: in function <....local/share/nvim/rocks/share/lua/5.1/rocks/command
s.lua:235>                                                                                                                                  
        [C]: at 0x01002b1bb8                                                                                                                
        [C]: in function 'pcall'                                                                                                            
        .../nvim/rocks/rocks_rtp/lua/rocks_treesitter/highlight.lua:48: in function 'callback'                                              
        ...share/nvim/rocks/share/lua/5.1/rocks/operations/init.lua:635: in function 'func'                                                 
        ...share/nvim/rocks/share/lua/5.1/rocks/operations/init.lua:42: in function <...share/nvim/rocks/share/lua/5.1/rocks/operations/init
.lua:41> 

So could this be some rocks-treesitter bug maybe? I for one is completely puzzled.

[mrcjkb]

Ahh, it is. rocks-treesitter still calls Rocks packadd 🤦‍♂️
Thanks for digging. 🙏

[mrcjkb]

Should be fixed now, after reinstalling rocks-treesitter.nvim.

lumen-oss/rocks-treesitter.nvim@09b24aa

[salkin-mada]

Thanks! Fantastic, we found it. I'm glad.