Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tree-sitter version update causes ABI version mismatch #347

Open
gmlarumbe opened this issue Mar 4, 2025 · 1 comment
Open

tree-sitter version update causes ABI version mismatch #347

gmlarumbe opened this issue Mar 4, 2025 · 1 comment

Comments

@gmlarumbe
Copy link

Hi,

Currently I am having some issues with the CI tests that run under verilog-ts-mode:

Warning (treesit): Cannot activate tree-sitter, because language grammar for verilog is unavailable (version-mismatch): 15

This started happening after using a newer version of the generated grammar parser with the latest tree-sitter-cli version (v0.25.2). After some debugging I believe this error is caused because Emacs would need to be recompiled since the ABI version generated with tree-sitter-cli v0.25.2 (15) is higher than the one used by Nix Emacs image (/nix/store/alq26qn1pys0fjpbam88j20v1zkych97-tree-sitter-0.24.6).

Would it be possible to update tree-sitter support to the latest version (v0.25.2)?

Related Reddit thread: https://www.reddit.com/r/emacs/comments/1cdb3r3/treesitter_modes_killing_my_emacs_session/

Thanks a lot!

@akirak
Copy link
Collaborator

akirak commented Mar 5, 2025

This project depends on the infrastructure of nixpkgs. Tree-sitter 0.25.1 was merged three weeks ago (see NixOS/nixpkgs#379367), but it has not landed nixpkgs-unstable yet. Can you wait until the update is propagated? It takes long because the tree-sitter update triggers rebuilds of thousands of packages.

You can check the status at https://nixpkgs-tracker.ocfox.me/?pr=379367. Once the status becomes green, we'll fire a workflow to update the nixpkgs dependency (or feel free to ping me if we haven't). Thanks for reporting this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants