I meet the similar problem yesterday, the error is 404, but I go through plugins installation, I meet 404 when list questions in leetcode-cli, it should be related to your vpn or shadowsocks, finally I didn't solve it. Now I use the leetcode extension in clion IDE,
just login in, nothing to wrong, you can start use.

I meet the similar problem yesterday, the error is 404, but I go through plugins installation, I meet 404 when list questions in leetcode-cli, it should be related to your vpn or shadowsocks, finally I didn't solve it. Now I use the leetcode extension in clion IDE,
just login in, nothing to wrong, you can start use.

meh, I am not using any VPN/ssr.

I meet the similar problem yesterday, the error is 404, but I go through plugins installation, I meet 404 when list questions in leetcode-cli, it should be related to your vpn or shadowsocks, finally I didn't solve it. Now I use the leetcode extension in clion IDE,
just login in, nothing to wrong, you can start use.

meh, I am not using any VPN/ssr.

I don't know why, as I'm not familar with js, I don't know how to find reason, so other ide may be a good choice.

@wnykuang get your point, let me have a check.

@wnykuang did you use proxy?

@yihong0618 nope, I didn't change any settings about the internet.

Could you open the URL?

https://raw.githubusercontent.com/leetcode-tools/leetcode-cli/master/lib/plugins/github.js

@yihong0618 nope, I didn't change any settings about the internet.

Could you open the URL?

https://raw.githubusercontent.com/leetcode-tools/leetcode-cli/master/lib/plugins/github.js

No, but its not the 404 url problem, github.js is the third party plugin which would not install usually, I have tried three different environment but I didn't locate your problem yet.

@yihong0618
interesting.

Do you need any more information?
like some npm call or so?

@yihong0618
interesting.

Do you need any more information?
like some npm call or so?

Yes what my guess is you use vscode-leetcode or leetcode-cli before and installed these third-party plugins maybe you are not notice, am I right?

@yihong0618
I have used leetcode-cli for years until last year I cannot log in anymore.
Do you know how to reset/delete the plugins?

@wnykuang
If so, can you make a test that remove the cache, use rm -rf ~/.lc/ and try to login again.

@yihong0618

after rm -rf ~/.lc/ the leetcode-vscode works!

Thank you!

@yihong0618
I have used leetcode-cli for years until last year I cannot log in anymore.
Do you know how to reset/delete the plugins?

My thinking is that use use third-party github.js and it saves in cache, and this time need to update caused these error.

@yihong0618 @zry656565 Seems that we need a way to make sure users are in a fresh env when they first use the extension. Like store some flags in the extension's global storage. If it's first time using the extension, clean the cache dir before activate

@yihong0618

after rm -rf ~/.lc/ the leetcode-vscode works!

Thank you!

My pleasure
@AndyYuan96 can you try this too?

@jdneo @zry656565
Can we make a popup on this error handling? Tell the user error hanpens and let user decide delete the cache or not.

        for (const plugin of supportedPlugins) {
            try { // Check plugin
                await this.executeCommandEx(this.nodeExecutable, [await this.getLeetCodeBinaryPath(), "plugin", "-e", plugin]);
            } catch (error) { // Download plugin and activate
                // popup
                await this.executeCommandEx(this.nodeExecutable, [await this.getLeetCodeBinaryPath(), "plugin", "-i", plugin]);
            }
        }

This is a good way to handle the error. While we also need a way to eliminate those errors at the first stage. For example, in the activate(), check if there is a certain flag in the global storage. If not, clean the cache, and generate the flag before the activate() finishes.