Skip to content
New issue

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

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

Already on GitHub? # to your account

Crashes on lsp-mode with version 0.5.4 #44

Closed
joefbkohler opened this issue Aug 23, 2022 · 11 comments
Closed

Crashes on lsp-mode with version 0.5.4 #44

joefbkohler opened this issue Aug 23, 2022 · 11 comments

Comments

@joefbkohler
Copy link

After updating to 0.5.4 csharp-ls crashes not long after initialization.

I don't know where to get a log, so if you need one please tell me where I can find it. The only error I get in stderr is Process csharp-ls stderr<1> finished

It crashes while moving the cursor, so my suspicion are either highlight or documentation.

@razzmatazz
Copy link
Owner

hey; I am tripping on this as well, debugging why -- will release a new version asap

@joefbkohler
Copy link
Author

Let me know if I can help.

@razzmatazz
Copy link
Owner

the cause is apparently this:

I am just trying to find a a way to avoid reverting this on the upstream and just fix csharp-ls with try/with in right places :)

razzmatazz added a commit that referenced this issue Aug 23, 2022
Previous commit on this apparently didn't do the job right.

Related:
- #44
@razzmatazz
Copy link
Owner

I have added this commit: 0641128 but not 100% that fixes it all

@razzmatazz
Copy link
Owner

razzmatazz commented Aug 23, 2022

@joefbsjr if you could test if the fix works for you then it would be really nice

because it does not hit it for me at once, it takes some incantation of requests to trigger the crash.. for some reason, so I am reluctant to declare victory yet :)

@joefbkohler
Copy link
Author

Sure. Will try later today.

@razzmatazz
Copy link
Owner

razzmatazz commented Aug 23, 2022

uh.. actually the error seems to be in upstream Ionide.LSP -- it marks LocalRpcException as fatal, but at the same time it uses it to report "error" lsp results.. ok, attempt no 2 at fixing this

@razzmatazz
Copy link
Owner

lets see if abdc323 helps

@razzmatazz
Copy link
Owner

@razzmatazz
Copy link
Owner

0.5.5 released that should fix this (I very much hope so):

@razzmatazz
Copy link
Owner

Closing, @joefbsjr please reopen if this occurs again

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

No branches or pull requests

2 participants