-
Notifications
You must be signed in to change notification settings - Fork 98
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
assertion failed: start.raw <= end.raw #303
Comments
Hey @psteinroe . So I checked the logs and did a bit more testing and it seems like it's not writing the unfinished string that causes it. It's if you file currently ends with a valid string, and you delete the identifier, it crashes.
|
And actually I'm not even sure it has anything to do with the string itself. Here you can see I just added and removed a space after it. 2025-04-04.123905.mp4 |
thanks for providing the details! if you are able to provide me the logfile from |
ah @Cikmo, I just realised that we removed the actual content in the logs… will fix that in the next release. if possible, please upgrade once its released and then send the logs through. will ping you! |
Alright |
the new release is out :) |
Here is the full server.log |
Bug report
Describe the bug
The language server crashes when entering an incomplete string at the end of the file.
Error message:
It seems to be triggered by typing an unfinished string or identifier at the end of the file.
For example writing out:
will instantly cause this error, exiting the program.
To Reproduce
Expected behavior
There should be a linter warning/error notifying the user there is an invalid string, rather than the program panicking.
System information
Linux
The text was updated successfully, but these errors were encountered: