Invalid Node Type in Neovim?
natdm opened this issue · 1 comments
natdm commented
Treesitter for neovim points to this repo as the standard query parser for elixir, so I figured I'd create an issue here to start.
Every time I open an elixir file, I get a few dozen of these errors:
E5108: Error executing lua ...im/0.5.1/share/nvim/runtime/lua/vim/treesitter/query.lua:161: query: invalid node
type at position 21
I've upgraded Neovim to 0.5.1, I've upgraded ts-elixir with :TSInstallSync elixir
, and ran :PackerUpdate
. Not sure what else to do.
Here's the :checkhealth
:
health#targets#check
========================================================================
- OK: No conflicting mappings found
health#telescope#check
========================================================================
## Checking for required plugins
- OK: plenary installed.
- OK: nvim-treesitter installed.
## Checking external dependencies
- OK: rg: found ripgrep 13.0.0
- OK: fd: found fd 8.2.1
## ===== Installed extensions =====
health#targets#check
========================================================================
- OK: No conflicting mappings found
health#nvim_treesitter#check
========================================================================
## Installation
- OK: `tree-sitter` found 0.20.0 (parser generator, only needed for :TSInstallFromGrammar)
- OK: `node` found v12.16.3 (only needed for :TSInstallFromGrammar)
- OK: `git` executable found.
- OK: `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
Version: Apple clang version 13.0.0 (clang-1300.0.29.3)
- OK: Neovim was compiled with tree-sitter runtime ABI version 13 (required >=13). Parsers must be compatible with runtime ABI.
## Parser/Features H L F I J
- json ✓ ✓ ✓ ✓ .
- elixir ✓ ✓ ✓ ✓ ✓
- c ✓ ✓ ✓ ✓ ✓
- lua ✓ ✓ ✓ ✓ ✓
- typescript ✓ ✓ ✓ ✓ ✓
- tsx ✓ ✓ ✓ ✓ ✓
- javascript ✓ ✓ ✓ ✓ ✓
- yaml ✓ ✓ ✓ ✓ ✓
- python ✓ ✓ ✓ ✓ ✓
- query ✓ ✓ ✓ ✓ ✓
Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
+) multiple parsers found, only one will be used
x) errors found in the query, try to run :TSUpdate {lang}
health#lspconfig#check
========================================================================
## Checking language server protocol configuration
- INFO: elixirls: configuration checked.
- INFO: gopls: configuration checked.
- INFO: efm: configuration checked.
- INFO: pyright: configuration checked.
- INFO: tsserver: configuration checked.
- INFO: sumneko_lua: configuration checked.
- INFO: vimls: configuration checked.
- ERROR: clangd: The given command "clangd" is not executable.
- ERROR: cmake: The given command "cmake-language-server" is not executable.
- ERROR: bashls: The given command "bash-language-server" is not executable.
health#nvim#check
========================================================================
## Configuration
- OK: no issues found
## Performance
- OK: Build type: Release
## Remote Plugins
- OK: Up to date
## terminal
- INFO: key_backspace (kbs) terminfo entry: key_backspace=^H
- INFO: key_dc (kdch1) terminfo entry: key_dc=\E[3~
- INFO: $TERM_PROGRAM='tmux'
- INFO: $COLORTERM='truecolor'
## tmux
- OK: escape-time: 10
- INFO: Checking stuff
- OK: focus-events: on
- INFO: $TERM: xterm-256color
- INFO: default-terminal: tmux-256color
- ERROR: $TERM differs from the tmux `default-terminal` setting. Colors might look wrong.
- ADVICE:
- $TERM may have been set by some rc (.bashrc, .zshrc, ...).
health#provider#check
========================================================================
## Clipboard (optional)
- OK: Clipboard tool found: pbcopy
## Python 2 provider (optional)
- INFO: `g:python_host_prog` is not set. Searching for python2 in the environment.
- INFO: Executable: /usr/bin/python2
- INFO: Python version: 2.7.16
- INFO: pynvim version: 0.4.3
- OK: Latest pynvim is installed.
## Python 3 provider (optional)
- INFO: `g:python3_host_prog` is not set. Searching for python3 in the environment.
- INFO: Multiple python3 executables found. Set `g:python3_host_prog` to avoid surprises.
- INFO: Executable: /usr/local/bin/python3
- INFO: Other python executable: /usr/bin/python3
- INFO: Python version: 3.9.7
- INFO: pynvim version: 0.4.3
- OK: Latest pynvim is installed.
## Python virtualenv
- OK: no $VIRTUAL_ENV
## Ruby provider (optional)
- INFO: Ruby: ruby 2.6.3p62 (2019-04-16 revision 67580) [universal.x86_64-darwin20]
- INFO: Host: /usr/local/bin/neovim-ruby-host
- WARNING: Gem "neovim" is out-of-date. Installed: 0.8.1, latest: 0.9.0
- ADVICE:
- Run in shell: gem update neovim
## Node.js provider (optional)
- INFO: Node.js: v12.16.3
- INFO: Nvim node.js host: /Users/Nathan.Hyland/.asdf/installs/nodejs/12.16.3/.npm/lib/node_modules/neovim/bin/cli.js
- OK: Latest "neovim" npm/yarn package is installed: 4.10.0
## Perl provider (optional)
- ERROR: perl provider error:
- ADVICE:
- "Neovim::Ext" cpan module is not installed
health#treesitter#check
========================================================================
## Checking treesitter configuration
- INFO: Runtime ABI version : 13
- OK: Loaded parser for c: ABI version 13
- OK: Loaded parser for elixir: ABI version 13
- OK: Loaded parser for javascript: ABI version 13
- OK: Loaded parser for json: ABI version 13
- OK: Loaded parser for lua: ABI version 13
- OK: Loaded parser for python: ABI version 13
- OK: Loaded parser for query: ABI version 13
- OK: Loaded parser for tsx: ABI version 13
- OK: Loaded parser for typescript: ABI version 13
- OK: Loaded parser for yaml: ABI version 13
- OK: Loaded parser for c: ABI version 13
- OK: Loaded parser for elixir: ABI version 13
- OK: Loaded parser for javascript: ABI version 13
- OK: Loaded parser for json: ABI version 13
- OK: Loaded parser for lua: ABI version 13
- OK: Loaded parser for python: ABI version 13
- OK: Loaded parser for query: ABI version 13
- OK: Loaded parser for tsx: ABI version 13
- OK: Loaded parser for typescript: ABI version 13
- OK: Loaded parser for yaml: ABI version 13
jonatanklosko commented
Hey @natdm! This repo is pretty standalone and not tied to any particular editor, so it's a nvim-treesitter thing in this case :) We've seen similar reports and it's currently tracked in nvim-treesitter/nvim-treesitter#1924, see if any of the comments helps, and otherwise feel free to add your notes there. Thanks!