Skip to content
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

Cannot execute CodeLens command using the "Show CodeLens Commands For Current Line" command: "actual command NOT FOUND" #139910

Closed
gnailuy opened this issue Dec 30, 2021 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug code-lens insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Milestone

Comments

@gnailuy
Copy link

gnailuy commented Dec 30, 2021

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.63.2 and 1.64.0-insider
  • OS Version: Windows 10 Enterprise 21H2 Build 19044.1415

Initially I found this issue on the Azure Stream Analytics extension, but I can also reproduce it on the CodeLens Sample extension which I think should provide a simpler environment to debug.

Steps to Reproduce (Using the CodeLens Sample extension):

  1. Clone the project source: https://github.com/microsoft/vscode-extension-samples
  2. cd to the codelens-sample directory;
  3. npm install then vsce package;
  4. Install the generated extension package codelens-sample-0.0.1.vsix;
  5. Open any file, the above extension provides CodeLens command "Codelens provided by sample extension" on every line;
  6. On any line, use Ctrl+Shift+P, then "Show CodeLens Commands For Current Line";
  7. Choose the CodeLens command then hit Enter;
  8. VSCode will show the below pop-up windows on the left-bottom corner;

image

  1. If we try step 6 and 7 a few more times, it will work eventually.

I see @jrieken resolved an issue #84153 which reported the same error message. So I also tried to debug this issue in the Developer Container. This issue is also related to the CodeLensCache, the cache key doesn't exist in the CodeLens cache. I'm not familiar with how the CodeLens cache works so the debug stuck here. Could you please help take a look? Thanks a lot.

image

@jrieken jrieken added bug Issue identified by VS Code Team member as probable bug code-lens labels Jan 3, 2022
@jrieken
Copy link
Member

jrieken commented Jan 3, 2022

I can reproduce in insiders but not when running out of dev. This error happens when code lens results are being disposed and that usually happens after a model or config change (anything that re-requests code lenses).

@jrieken jrieken added this to the January 2022 milestone Jan 3, 2022
@jrieken jrieken closed this as completed in b5d3ec5 Jan 3, 2022
sourcegraph-bot pushed a commit to sgtest/megarepo that referenced this issue Jan 3, 2022
Commit: b5d3ec5b49554bea1d7e1bc372ac8705595b98c4
@gnailuy
Copy link
Author

gnailuy commented Jan 5, 2022

Thank you so much for the quick fix. I've verified it works well in VSCode Insiders.

@jrieken jrieken added the verified Verification succeeded label Jan 5, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Feb 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug code-lens insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants
@gnailuy @jrieken and others