Closed MAGNAT2645 closed 5 months ago
Hello! Thanks for reporting this, I was looking for a way to replicate the issue!
What's probably happening is that there is a mistake in the lexer grammar somewhere in the preprocessor, that causes it to to one token too far.
Would it be possible for you to send me one of the workspace that crashes your lsp please? With all the files
I found possible issue.
#pragma deprecated "Устаревшая функция. Плагин автоматически очищает всё, что создал другой выгруженный плагин."
If i comment out this line, extension doesn't crash.
So i guess this happens due to using Unicode symbols (but the compiler itself seems to support these).
But this one is starting to annoy every time i open workspaces.
Failed to run spcomp. No such file or directory (os error 2)
Thanks for helping me replicate this! Fixed in https://github.com/Sarrus1/sourcepawn-lexer/releases/tag/0.1.2 I will merge this when I merge feat/salsa (which might take some time...)
Fixed in v7.1.0, which is stable.
Basic informations
Further Information
The extension started to crash and stops loading after 5 crashes. Log says
Invalid Lexer bump
. Happened today and still happening, was working fine earlier.There's also another error but it doesn't break anything, just annoying.
Failed to run spcomp. No such file or directory (os error 2)
This error happens only when you open (or switch to) any workspace (or just restart LSP).SourcePawnLanguageServer.spcompPath
is set up tospcomp
with absolute path and compiling using Ctrl+Shift+D works fine.To Reproduce
Just open any workspace or restart LSP. That's all.
Code to reproduce the behaviour
None.
Expected behaviour
Extension should not crash like this. I don't know what could have been changed to make the extension crash now.
Error messages
I guess these crashes happen due to assert check in the logos package (
lexer.rs
) but idk how to fix this