ionide-vscode-fsharp
ionide-vscode-fsharp copied to clipboard
ionide
"!!MISSING: Command" after upgrade to 5.9.0
After upgrade to 5.9.0 I'm seeing !!MISSING: Command in code lens for every line.
Downgrading Ionide back to 5.8.1 fixed the issue.
This is a ssh-remote seession from Linux to Linux, both with dotnet 5.0.402.
Hey @pkese :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:
![open-collective-bot[bot] avatar](https://avatars.githubusercontent.com/in/23739?v=4 "Published by a pub.dev verified publisher"){kind=small}
Seeing this, too. I'm on Windows. Also - switching from CodeLens to Line Lens fixes the issue.
If anyone is able to verify this issue is resolved by the PR I submitted here, I can open the 'real' one on FSAC as well/instead. (More info in the PR)
Closing, as this was implemented by @beauvankirk and released as part of 5.9.1.
@beauvankirk @baronfel
I'm still getting this with Ionide 5.9.1. But what is really interesting is that after a while it starts working for new files that I open.
It is as if the FSAC takes a while to start responding to Ionides' requests (that's just my hypothesis, there may be other causes) and everything that Ionide analyzes up to that point is presented as "!!MISSING: Command!! | !!MISSING: Command!!".
But files that I open later get proper code lens hints.
Problem is that Ionide caches those initial 'missing' responses and won't update.
And sometimes it resolves some lines completely and some just partially:
- both references and type on the top
- only type on the bottom
No. My hypothesis was wrong. It's not that after a while FSAC starts working... rather it stays inconsistent. Sometimes it works, then after a while I open another file and it doesn't.
I am seeing this on multiple Windows PC's using 6.0.6. But it's working ok editing a project on WSL.
Can reproduce it in 7.3.0:
Switching to LineLens doesn't help - the info just disappears altogether.
Any workaround for this?
@psfinaki I've found out that sometimes, I'd just close that editor (file within the project) and open it again and it would display normally ... as if it's just initial load that fails to work. Is that your experience as well?
@pkese well yes, just what you say - sometimes it helps :) which is, well, annoying and mysterious.
I am still getting this or other similar issues across multiple PC's. I keep wanting to make use of VS Code + Ionide for projects but sadly it seems that 80+% of the time (across multiple systems) it's just non-functional so I must stick with full VS 😒
I just tried various combinations of closing and opening, closing restarting, and then opening the editor on this new PC with recent fresh installs of everything, and it's just the MISSING command and no intellisense.
Is there some procedure for capturing detailed diagnostics that will pinpoint what is configured wrongly on this device? What do I have installed that's the wrong version? What did I install in the wrong order?
I am still getting this or other similar issues across multiple PC's. I keep wanting to make use of VS Code + Ionide for projects but sadly it seems that 80+% of the time (across multiple systems) it's just non-functional so I must stick with full VS 😒
I just tried various combinations of closing and opening, closing restarting, and then opening the editor on this new PC with recent fresh installs of everything, and it's just the MISSING command and no intellisense.
Is there some procedure for capturing detailed diagnostics that will pinpoint what is configured wrongly on this device? What do I have installed that's the wrong version? What did I install in the wrong order?
Adding a global.json to block use of preview SDK's seems to have resolved it.
But this makes it difficult to experiment with new .Net 7 features.