-
Notifications
You must be signed in to change notification settings - Fork 37
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
F# Language Server crashed 5 times in the last 3 minutes #43
Comments
Those conflict messages are normal, .net project rules are very complicated and we have to rely on heuristics to resolve ambiguities. Those conflict warnings are logging the choices we're making. If you could make a minimal example that reproduces the problem, that would help diagnose. As it is, it's hard to tell what caused the crash---everything up to |
Sorry for the late response. Thanks for getting back and I'll try to see if I can reproduce it with a much smaller application by slowly removing files. I'll post it here when I have something for you to look at. Also I think #45 might be related. |
Having the same trouble. Not really even sure how to get diagnostics, the VSCode command to show logs is also bombing out. |
Faced this problem too. By default Ionide installs version 5.xx. Solved by installing previous one (4.17) |
@WhiteSharq note that this repo is not the Ionide repo. Any notes about it should go to Ionide/ionide-vscode-fsharp. |
If helps anyone, I had this problem after cloning the SAFE dojo repo. I just opened vscode in a child folder, I wasn't at the root of the project. |
It's been a year since this is not fixed. I've tried everything mentioned in this repo and github.com/ionide/ionide-vscode-fsharp and this message about the server crashing is still there. |
It's probably Ionide failing, not this project. Please direct all ire over onto the Ionide repo. |
Hi,
I installed this extension to test it on one of my projects but after opening my project in VSCode the F# Language Server crashed almost immediately and keeps crashing when I restart VSCode.
The message is:
Looking through the logs, it seems that it picked up the
Core.fs
file of my project first, then was scanning for projects which reference this file and started to crack open the one.fsproj
which has this file.I notice many conflicts during dependency resolution which are like this:
The text was updated successfully, but these errors were encountered: