command 'leetcode.toggleLeetCodeCn' not found

[yanite]

Environment

• os: windows 10
• extension settings:
• nodejs version: v11.11.0
• vscode version: 1.32.1
• extension version: 0.12.0

安装没问题点击面板上的一切都报这个错误

[jdneo]

Please check the document here to see if it could help: https://github.com/jdneo/vscode-leetcode/wiki/%E7%96%91%E9%9A%BE%E8%A7%A3%E7%AD%94#thinking-%E6%8F%90%E7%A4%BA%E9%94%99%E8%AF%AF-command-leetcodexxx-not-found

[qianchanger]

I also have this problem......

• mac 10.13.4
• vscode 1.32.3
• nodejs v11.11.0
  

[qianchanger]

The above documentation does not seem to contain this problem

[qianchanger]

switch this leetcode-plugin to 0.12 version , it works. :)

[Yihemu]

switch this leetcode-plugin to 0.12 version , it works. :)

it can't work

[jdneo]

Not sure if this is related to this issue: #201

For example, you are using a third-party bash, like zshell, and your node.js is only available in the zshell, not the default bash.

Then the extension will not run the leetcode command successfully since it will spawn a child process from the default bash.

[Yihemu]

But i haven't used a third-party bash.

[jdneo]

Have you tried this: https://github.com/jdneo/vscode-leetcode/wiki/%E7%96%91%E9%9A%BE%E8%A7%A3%E7%AD%94#thinking-%E6%8F%90%E7%A4%BA%E9%94%99%E8%AF%AF-command-leetcodexxx-not-found

[Yihemu]

Have you tried this: https://github.com/jdneo/vscode-leetcode/wiki/%E7%96%91%E9%9A%BE%E8%A7%A3%E7%AD%94#thinking-%E6%8F%90%E7%A4%BA%E9%94%99%E8%AF%AF-command-leetcodexxx-not-found

[ybtuteng]

today I met this error too
vscode:1.32.3
node:10.15.1
mac os:10.14.3
I use mac's terminal as default shell
yesterday everything is ok, and I have used it for a week normally
but today it cannot work suddenly

[jdneo]

Emm, suspecting related with #211. We will release a release recently.

[jdneo]

I'm closing this issue for now since this issue should be fixed with #212.

We will release the fix recently in 0.13.1.

If you still have problems after using 0.13.1, please feel free to let us know.

[com3345]

Same problem..

• os: win10 1803
• vs code version: 1.32.3
• node.js version: 10.15.3
• extension LeetCode version: 0.13.1
• And I don't have any other bashes except default powershell/cmd.

I'm wondering if the proxy setting leads to the situation:

[jdneo]

@Vigilans Any ideas?

[Vigilans]

But i haven't used a third-party bash.

@Yihemu why is the command toogleLeetCodeCn Σ( ° △ °|||)︴?

It seems that this bug is caused by the failure of initialization in extension's main entry.

Several reasons that may cause activate's early exit:

• leetCodeExecutor.meetRequirements return false and activate exits directly.

    if (!await leetCodeExecutor.meetRequirements()) {
        return;
    }

  There will be messages in the output channel if the bug is triggered for this reason.
  @ALL Could you please provide the content by pressing Ctrl+Shift+U and toggle the channel from Tasks or 任务 to LeetCode?

• Some other exception is triggered in the rest part of initialization. It is a grief that the exception content won't get processed by leetCodeChannel.

@jdneo I think we may provide a try ... catch block in activate, and let LeetCodeChannel output the error message, at the same time showing a prompt saying Extension initialization failed, along with a button to guide them to the output channel?

[ShannonGu]

I also encountered the problem, then I install the old version, and it works.

[jdneo]

@ShannonGu Please try 0.13.3

[ShannonGu]

@jdneo um.....0.13.3 suddenly works. Thanks!

[HeronWan]

I also encountered the problem

[WincentZhang]

The same question, Oh god! no way to finish?

[xuxinyang]

Does someone fix it?

[xuxinyang]

I just restart VScode some times, it's works!

[yhaoyan]

I'm closing this issue for now since this issue should be fixed with #212.

We will release the fix recently in 0.13.1.

If you still have problems after using 0.13.1, please feel free to let us know.

I use v0.17.0 but meet the mistake again..
Please help

[coco8514]

[zhongyangxun]

It works on my Windows 10 machine by restarting VS Code.