2

The problem occurs when one of the long running command is forcefully killed by process.kill

After that whenever I try to execute a command it raise Command 'extension.commandName' not found error.

Note: All the commands are properly registered in package.json under contribution>>command. Commands are also included as part of activationEvents. Keybinding also in place for the registered command. I have also checked similar issues like this but that did not cover my scenario.

1 Answer 1

2

The way I am handling this right now is by exposing another command that fires workbench.action.reloadWindow. Once the window is reloaded the extension able to handle request again.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.