-
Notifications
You must be signed in to change notification settings - Fork 76
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
"The OCaml Platform VS Code extension server crashed 5 times in the last 3 minutes" #818
Comments
Hi, can you open the output pane in vscode, set the "OCaml Language Server" in the dropdown and tell us why ocaml-lsp is crashing? See the screenshot for what "output pane" is and the value set for the dropdown: Is the |
Not sure, I just grabbed it from
Ah, it seems like an issue with the reason version. My
|
@let-def how should we catch errors like this? Can we assume that every |
In this case Merlin will never be able to process AST sent by reason. The internal state is not corrupted, but Merlin won't give any useful information until reason is fixed. |
Could you make it a specific exception? E.g. |
Sounds good, I will add that. |
Thank you! |
Fixed in ocaml/ocaml-lsp#608 |
Thanks for the awesome extension. It was working fine, but recently I've been getting this popup:
I'm using esy, with
@opam/ocaml-lsp-server@opam:1.9.1@1397dba9
as a devdependency. The problem persists after uninstalling and reinstallingocamllabs.ocaml-platform
, quitting vscode, etc. (I have the extension configured to use the esy sandbox.)The text was updated successfully, but these errors were encountered: