Treesitter integration broken on Javascript about vim-matchup

[andymass]

Just merged this:
#306

Did it fix it?

[bmulholland]

It did! Fast work -- thank you!

I was just tracking it down, but seems like disabling treesitter integration didn't solve it? Just made it less frequent. Bit odd.

Anyway, fixed now, thank you!

[riverajohan]

Im still experiencing this bug when the cursor is at the opening or close of a parenthesis ()

[andymass]

@riverajohan have you done :TSUpdate?

[idevat]

I've got similar issue after update #306. I fixed it by using 'commit': '3c4ccc489002fe72b5d2e2ffc4b3b5a7d3ab65d8' in plug definition.
My neovim version is v0.9.1. I had this issue before and I fixed it by using 'tag': 'v0.9.0' for neovim-treesitter.
Is there also a tag for specific neovim version?

[riverajohan]

@riverajohan have you done :TSUpdate?

Yes I did. Then uninstall / install with no luck. I just reverted to a previous version of the plugin. Im using Lunarvim maybe its related to that but im ok not using the latest update. Thanks

[gipo355]

can confirm: matchup broken in javascript.
spawns an error on every cursor move

Error detected while processing CursorMoved Autocommands for "*"..function 3[3]..4[71]..matchup#delim#get_current[1]..<SNR>96_get_delim_multi[3]..matchup#ts_engine#get_delim[3]..<SNR>91_forward:
     1 line    1:
     2 E5108: Error executing lua /usr/share/nvim/runtime/lua/vim/treesitter/query.lua:273: query: invalid node type at position 1172 for language javascript
     3 stack traceback:
     4   [C]: in function '_ts_parse_query'
     5   /usr/share/nvim/runtime/lua/vim/treesitter/query.lua:273: in function 'parse'
     6   /usr/share/nvim/runtime/lua/vim/treesitter/query.lua:232: in function 'get_query'
 ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:55: in function 'get_query'
     1   ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:142: in function 'prepare_query'
     2   ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:339: in function 'iter_group_results'
     3   ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:351: in function 'collect_group_results'
     4   ...lazy/opt/vim-matchup/lua/treesitter-matchup/internal.lua:46: in function 'fn'
     5   /usr/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:384: in function 'for_each_tree'
...lazy/opt/vim-matchup/lua/treesitter-matchup/internal.lua:40: in function 'fn'
     1   ...azy/opt/nvim-treesitter/lua/nvim-treesitter/ts_utils.lua:380: in function 'get_matches'
     2   ...lazy/opt/vim-matchup/lua/treesitter-matchup/internal.lua:102: in function 'fn'
     3   ...azy/opt/nvim-treesitter/lua/nvim-treesitter/ts_utils.lua:380: in function 'get_active_nodes'
     4   ...lazy/opt/vim-matchup/lua/treesitter-matchup/internal.lua:221: in function 'get_delim'
     5   [string "luaeval()"]:1: in main chunk

:TSUpdate everything is updated, js parser installed

edit:
tried 'commit': '3c4ccc489002fe72b5d2e2ffc4b3b5a7d3ab65d8' and it works so possibly a bad commit bisect after that

[rbjorklin]

I'm seeing a very similar issue that shows up on lua files. The issue I'm seeing was introduced in b8eca3b.

Error detected while processing CursorMoved Autocommands for "*"..function 3[3]..4[71]..matchup#delim#get_current[1]..<SNR>75_get_delim_multi[3]..matchup#ts
_engine#get_delim[3]..<SNR>72_forward:
line    1:
E5108: Error executing lua /usr/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 6 for language lua
stack traceback:
        [C]: in function '_ts_parse_query'
        /usr/share/nvim/runtime/lua/vim/treesitter/query.lua:259: in function 'get_query'
        ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:55: in function 'get_query'
        ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:142: in function 'prepare_query'
        ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:339: in function 'iter_group_results'
        ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:351: in function 'collect_group_results'
        ...er/start/vim-matchup/lua/treesitter-matchup/internal.lua:46: in function 'fn'
        /usr/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:341: in function 'for_each_tree'
        ...er/start/vim-matchup/lua/treesitter-matchup/internal.lua:40: in function 'fn'
        ...r/start/nvim-treesitter/lua/nvim-treesitter/ts_utils.lua:380: in function 'get_matches'
        ...er/start/vim-matchup/lua/treesitter-matchup/internal.lua:102: in function 'fn'
        ...r/start/nvim-treesitter/lua/nvim-treesitter/ts_utils.lua:380: in function 'get_active_nodes'
        ...er/start/vim-matchup/lua/treesitter-matchup/internal.lua:221: in function 'get_delim'
        [string "luaeval()"]:1: in main chunk

[0rtz]

Seeing same issue in c files with treesitter + matchup enabled

[amaanq]

C is fixed now

[cova-fe]

I'm seeing apparently the same problem while opening the config.lua (lunarvim)
Error detected while processing CursorMoved Autocommands for "*"..function 3[3]..4[71]..matchup#delim#get_current[1]..<SNR>65_get_delim_multi[3]..matchup#ts_engine#get_delim[3]..<SNR>60_forward: line 1: E5108: Error executing lua /usr/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 6 for language lua stack traceback: [C]: in function '_ts_parse_query' /usr/share/nvim/runtime/lua/vim/treesitter/query.lua:259: in function 'get_query' ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:55: in function 'get_query' ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:142: in function 'prepare_query' ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:339: in function 'iter_group_results' ...vim-matchup/lua/treesitter-matchup/third-party/query.lua:351: in function 'collect_group_results' ...lazy/opt/vim-matchup/lua/treesitter-matchup/internal.lua:46: in function 'fn' /usr/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:341: in function 'for_each_tree' ...lazy/opt/vim-matchup/lua/treesitter-matchup/internal.lua:40: in function 'fn' ...azy/opt/nvim-treesitter/lua/nvim-treesitter/ts_utils.lua:380: in function 'get_matches' ...lazy/opt/vim-matchup/lua/treesitter-matchup/internal.lua:102: in function 'fn' ...azy/opt/nvim-treesitter/lua/nvim-treesitter/ts_utils.lua:380: in function 'get_active_nodes' ...lazy/opt/vim-matchup/lua/treesitter-matchup/internal.lua:221: in function 'get_delim' [string "luaeval()"]:1: in main chunk

[amaanq]

You need to ensure your plugins are up to date and tree-sitter parsers as well with :TSUpdate

[gipo355]

My parsers are up to date and I still can't use the plugin in JavaScript files as it triggers the error on every cursor move

[amaanq]

can't reproduce in a js file - a reproducer w/ steps would be useful

[cova-fe]

Just checked: Forcing nvim-treesitter to latest commit, followed by TSUpdate seems to have fixed the issue. So if someone else is experiencing similar issues, it is worth to have a look at nvim-treesitter plugin status

[amaanq]

right...updating it to the latest commit = updating the plugin

[kohane27]

My bad. Turned out I can't lazy load vim-matchup with lazy.nvim

[crabsinger]

I'm getting this same type of error with lua files

[riverajohan]

I can confirm this is fixed.

[titanve]

I'm still getting this error

[riverajohan]

I'm still getting this error

Validate you have an updated version of treesitter. In my case I was using Lunarvim on the 1.3 release. That release have the plugins version locked to a pretty old version and that was the cause for the error for me. I moved to the master branch and after the update the issue was fixed.

[titanve]

@riverajohan Hi!
I can see in my lazy-lock.json file that I have this for treesitter "nvim-treesitter": { "branch": "master", "commit": "2ce3c9080cfe4a39c7907e672edafd2a95244a7c" }, Is this ok?

Thanks

[titanve]

I changed the commit SHA to this one 208504c7072ca81e8bf9fa2e666cf3436dfc0ef5 (latest) in the lazy-lock.json file and then LunarVim reverted it back again to 2ce3c9080cfe4a39c7907e672edafd2a95244a7c

How may I change the version/SHA?

[riverajohan]

I changed the commit SHA to this one 208504c7072ca81e8bf9fa2e666cf3436dfc0ef5 (latest) in the lazy-lock.json file and then LunarVim reverted it back again to 2ce3c9080cfe4a39c7907e672edafd2a95244a7c

How may I change the version/SHA?

What I did was installing lunarvim from the Master branch. https://www.lunarvim.org/docs/master/installation#nightly

[titanve]

@riverajohan hi!

Do you mean the nightly version?

Thanks

[riverajohan]

@riverajohan hi!

Do you mean the nightly version?

Thanks

Yes