Skip to content

unable to activate the extension. #247

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
LucaPractice opened this issue Apr 1, 2019 · 14 comments
Closed

unable to activate the extension. #247

LucaPractice opened this issue Apr 1, 2019 · 14 comments

Comments

@LucaPractice
Copy link

您好,我的vscode版本为1.32.3,nodejs版本为10.15.3,使用插件时仍然有command 'leetcode.xxx' not found的错误提示。

@jdneo jdneo changed the title 满足运行条件后仍然无法加载插件 unable to activate the extension. Apr 1, 2019
@jdneo
Copy link
Member

jdneo commented Apr 1, 2019

Is there any logs in the console if you open Help > Toggle Developer Tools

@jdneo jdneo added the need more info Further information is requested label Apr 1, 2019
@Vigilans
Copy link
Contributor

Vigilans commented Apr 1, 2019

What will be shown if you click the leetcode icon on the left activity bar?

Besides, is there any output message if you press Ctrl+Shift+U and toggle the channel from Tasks or 任务 to LeetCode?

@jdneo
Copy link
Member

jdneo commented Apr 1, 2019

@LucaPractice Just feel free to comment on the root cause and how you solve the problem. This information could help other users who also encounter the same problem.

Thanks.

@deadoggy
Copy link

deadoggy commented Apr 3, 2019

I meet the same problem. The day before yesterday I could use the extension normally, today it fails. There is a "There is no data provider registered that can provide view data." on the sidebar and there is "leetcode.xxx not found"
. My environment is ubuntu 18.04lts + vscode 1.32.3 + node 10.15.3 .

Here is my log:

Screenshot from 2019-04-03 17-32-35

@deadoggy
Copy link

deadoggy commented Apr 3, 2019

@jdneo Thanks!

@jdneo
Copy link
Member

jdneo commented Apr 3, 2019

@deadoggy I guess the root cause is that the installed files are corrupted. Try to uninstall the extension and remove it. You should be able to find it under $HOME/.vscode/extensions. Remove the folder shengchen.vscode-leetcode-* and reinstall it.

Please let me know if this could help solve your problem.

@deadoggy
Copy link

deadoggy commented Apr 3, 2019

@jdneo I uninstalled the extension and removed the folder under ~/.vscode/extensions/, but the problem still exists. Here is the console screenshot:

Screenshot from 2019-04-03 22-41-39

It's almost the same as the prior one.

@jdneo
Copy link
Member

jdneo commented Apr 4, 2019

Ah, Have no ideas so far.

But I noticed that there is some other strange output in the console:
image

Not sure if it is something wrong with your environment.

@Vigilans Do you have any ideas?

@Vigilans
Copy link
Contributor

Vigilans commented Apr 4, 2019

Found the problem.

image
@deadoggy The line 6 is require("./LeetCodeStatusBarItem"), the first letter to be upper case L.

However, in the published extension, there is

image

the first letter to be lower case l.

Ubuntu file name is case-sensitive, resulting in the NotFound problem.


@jdneo btw, I checked the folder structure in the extension folder and found another thing strange:

image

So there are two problems with the published extension:

  • wrong letter case of out/src/statusbar/leetcodeStatusBarItem.js
  • redundant file out/src/leetcodeStatusBarItem.js

@Vigilans Vigilans reopened this Apr 4, 2019
@LucaPractice
Copy link
Author

I made a low-level mistake. I installed the extension first and then installed nodejs. I found that I can't use it and I reinstalled the extension. I did not restart the vscode after uninstalling the extension, so I can't use it after reinstalling the extension.

@no-response no-response bot removed the need more info Further information is requested label Apr 4, 2019
@z774379121
Copy link

@Vigilans
It can be work when I use upper case L in out/src/statusbar/leetcodeStatusBarItem.js:6:33
Thanks!

@deadoggy
Copy link

deadoggy commented Apr 4, 2019

@jdneo @Vigilans It works after changing 'l' to 'L'. Thanks a lot!

@jdneo
Copy link
Member

jdneo commented Apr 4, 2019

@ALL

@Vigilans and I are working on releasing a hotfix 0.13.3 for this issue.

@jdneo
Copy link
Member

jdneo commented Apr 4, 2019

0.13.3 released. Please feel free to let us know if you still meet the problem.

Thanks.

@jdneo jdneo closed this as completed Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants