fix(treesitter): check buffer validity before enabling features#70
Merged
Merged
Conversation
When treesitter parser installation is triggered asynchronously (e.g., via auto_install), the buffer may be deleted before the installation completes and the callback is executed. This can happen when using plugins like flatten.nvim that open files in a guest process and then delete buffers before sending them to the host. This race condition results in an "Invalid buffer id" error when the async callback tries to enable treesitter features on a buffer that no longer exists. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Author
|
@mehalter @astronvimbot Hello. Please review the pr. I met a treesitter error when merged to |
mehalter
approved these changes
Apr 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When treesitter parser installation is triggered asynchronously (e.g., via auto_install), the buffer may be deleted before the installation completes and the callback is executed. This can happen when using plugins like flatten.nvim that open files in a guest process and then delete buffers before sending them to the host.
This race condition results in an "Invalid buffer id" error when the async callback tries to enable treesitter features on a buffer that no longer exists.
📑 Description
📖 Additional Information