"!!MISSING: Command" after upgrade to 5.9.0

[pkese]

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.

[open-collective-bot]

Hey @pkese 👋,

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 backer support for all backers. Don't forget to add backer label when you start backing us 😄

[isaacabraham]

Seeing this, too. I'm on Windows. Also - switching from CodeLens to Line Lens fixes the issue.

[ed-ilyin]

Same on MacOS and dotnet 6

[beauvankirk]

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)

[baronfel]

Closing, as this was implemented by @beauvankirk and released as part of 5.9.1.

[pkese]

@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.

[pkese]

And sometimes it resolves some lines completely and some just partially:

• both references and type on the top
• only type on the bottom
  

[pkese]

Unfortunately I can't reopen the ticket.

[pkese]

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.