-
-
Notifications
You must be signed in to change notification settings - Fork 66
Fix unsafe lspclient access #334
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
Conversation
|
Thanks for the PR. I think I have a slightly different fix for this issue. As we are obsoleting lspconfig. I will remove the if/else check. |
|
Regrettably, this commit did not work for me. I tried making some changes: if default_config == nil then
default_config = {}
endCrude, but it worked(Of course, with an empty config block) |
Makes sense, but yes this issue is still present in the latest master, stack trace: ❯ git log HEAD
commit 546982c1e4be3f6b56f0ebe4cd234073565bcadb (HEAD -> master, origin/master, origin/HEAD)
Author: ray-x <rayx.cn@gmail.com>
Date: Wed Oct 29 11:57:55 2025 +1100
remove require('lspconfig') as it is obseleted |
That's strange as the Mind posting the entire stack trace? |
The same. |
|
Sorry, I was meant to commit to master; however, it was pushed to treesitter-main branch I have redone the commit, and it should work now. |
|
It does! |
Fixes #333