No Intellisense , hover showing, cannot display either the F# Explorer side view or the info panel - all of the above used to work
windows 10
VSCode v 1.36.1 (user setup)
Ionide 4.0.6 but have also tried reverting to 4.0.4
Dotnet sdk 2.2.301
With verbose logging switched on I have the following example messages:
[LSP call] TextDocumentHover
[LSP] PositionHandler - Position request: d:/Source/Repos/RevocationOrchestration/TokenRevocation/configurationSettings.fs at (17,10)
[FSharpChecker] Current Queue Length: 0
[Checker] TryGetRecentCheckResultsForFile - d:\Source\Repos\\RevocationOrchestration\TokenRevocation\configurationSettings.fs
[LSP] PositionHandler - Cached typecheck results not yet available
[Error - 20:58:26] Request textDocument/hover failed.
Message: Cached typecheck results not yet available
Code: -32603
This doesn't appear to be related to unexpected char in path to file
I'm also seeing with same in vs code insiders with the ionide experimental extension so I think its environment but I'm not sure what else to check in terms of processes that should be running or pre -reqs
Hey @richardjharding :wave:,
Thank you for opening an issue. We will get back to you as
soon as we can. Also, check out our OpenCollective and consider
backing us.
https://opencollective.com/ionide
PS.: We offer
backersupport for all backers. Don't forget to addbackerlabel when you start backing us :smile:
Hello,
I had the same issue.
I solved it by deleting all .ionide folder above my workspace.
Deleting .ionide only in workspace root was not enough
Hey, I'd start with removing the .ionide folder as suggested by @rfrerebe and with removing any bin and obj folders in your project folders.
Hello,
Also if you have a sln file in your directory without your FSharp project,
it could also create this issue.
Solution is either to add fsproj to sln
dotnet sln add ./path/to/fsproj
Or remove sln file...
If you happen to work on csproj in Visual and fsproj in vs code, Visual
will create a sln for you and Ionide will stop working. I believe this is
by design, but it’s easy to forget this ...
Le mar. 17 sept. 2019 à 19:19, Krzysztof Cieślak notifications@github.com
a écrit :
Hey, I'd start with removing the .ionide folder as suggested by @rfrerebe
https://github.com/rfrerebe and with removing any bin and obj folders
in your project folders.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ionide/ionide-vscode-fsharp/issues/1185?email_source=notifications&email_token=ADAMGIK3DOLEU3SHEB5KOKDQKEGQFA5CNFSM4IFLOASKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65IEIY#issuecomment-532316707,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADAMGIN3ADZPA2NOQUQMURDQKEGQFANCNFSM4IFLOASA
.
Yes, sln behavior is by-design, indeed. If we detect sln file in workspace we load that by-default, otherwise we try to find all fsproj files in the workspace.
When I updated to 4.4.0, I have no intellisense / line lense / tool tips at all. Switches FSAC to core / netfw didn't have any effect.
I can reproduce this very easily: Create a new folder, open that in VSCode, create an empty fsx file and paste this code:
```open System
let x = 42
F# output:
[Error - 10:16:34] Request textDocument/documentSymbol failed.
Message: File 'c:\Temptesttest.fsx' not parsed
Code: -32603
[Error - 10:17:37] Request textDocument/hover failed.
Message: File 'c:\Temptesttest.fsx' not parsed
Code: -32603
[Error - 10:17:39] Request textDocument/hover failed.
Message: File 'c:\Temptesttest.fsx' not parsed
Code: -32603
[Error - 10:17:39] Request textDocument/hover failed.
Message: File 'c:\Temptesttest.fsx' not parsed
Code: -32603
```
@ronaldschlenker, should be working again in 4.4.1
Wow, thanks @Krzysztof-Cieslak. That was quick. After Christmas, I try to finally set up a running dev environment for Ionide, so that I'm able to contribute some smaller things from time to time. Thanks again for your work. I have open collective donation on my TODO list for this year :)
From my POV, you can close this. It's fixed.
Most helpful comment
Wow, thanks @Krzysztof-Cieslak. That was quick. After Christmas, I try to finally set up a running dev environment for Ionide, so that I'm able to contribute some smaller things from time to time. Thanks again for your work. I have open collective donation on my TODO list for this year :)