Skip to content

command 'leetcode.toggleLeetCodeCn' not found #203

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

Closed
yanite opened this issue Mar 13, 2019 · 25 comments
Closed

command 'leetcode.toggleLeetCodeCn' not found #203

yanite opened this issue Mar 13, 2019 · 25 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@yanite
Copy link

yanite commented Mar 13, 2019

Environment

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

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

@jdneo
Copy link
Member

jdneo commented Mar 13, 2019

@jdneo jdneo added the need more info Further information is requested label Mar 15, 2019
@qianchanger
Copy link

I also have this problem......

  • mac 10.13.4
  • vscode 1.32.3
  • nodejs v11.11.0
    image

image

@qianchanger
Copy link

The above documentation does not seem to contain this problem

@qianchanger
Copy link

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

@Yihemu
Copy link

Yihemu commented Mar 16, 2019

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

it can't work

@jdneo
Copy link
Member

jdneo commented Mar 16, 2019

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
Copy link

Yihemu commented Mar 16, 2019

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

@ybtuteng
Copy link

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
image
image

@jdneo
Copy link
Member

jdneo commented Mar 17, 2019

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

@jdneo
Copy link
Member

jdneo commented Mar 17, 2019

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.

@jdneo jdneo closed this as completed Mar 17, 2019
@jdneo jdneo added bug Something isn't working duplicate This issue or pull request already exists and removed need more info Further information is requested labels Mar 17, 2019
@com3345
Copy link

com3345 commented Mar 30, 2019

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:

image

@jdneo
Copy link
Member

jdneo commented Mar 31, 2019

@Vigilans Any ideas?

@Vigilans
Copy link
Contributor

Vigilans commented Apr 1, 2019

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
Copy link

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

@jdneo
Copy link
Member

jdneo commented Apr 4, 2019

@ShannonGu Please try 0.13.3

@ShannonGu
Copy link

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

@HeronWan
Copy link

I also encountered the problem

@WincentZhang
Copy link

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

@xuxinyang
Copy link

Does someone fix it?

@xuxinyang
Copy link

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

@yhaoyan
Copy link

yhaoyan commented Sep 29, 2020

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

image

@coco8514
Copy link

coco8514 commented Jan 6, 2021

Screen Shot 2021-01-05 at 10 32 08 PM

@zhongyangxun
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests