Failed to load locked problem

[yuzhoul1991]

Problem Summary

It is no longer able to show and download the locked questions all of a sudden. I am still premium member.

How to reproduce

$ leetcode show 298 -g -vv ⬡ 9.4.0
[TRACE] initializing all plugins
[TRACE] found plugin: cache=default
[TRACE] inited plugin: cache
[TRACE] found plugin: company=2017.12.18
[TRACE] inited plugin: company
[TRACE] found plugin: cpp.run=2017.07.29
[TRACE] inited plugin: cpp.run
[TRACE] found plugin: github=2018.01.06
[TRACE] inited plugin: github
[TRACE] found plugin: leetcode=default
[TRACE] inited plugin: leetcode
[TRACE] found plugin: retry=default
[TRACE] inited plugin: retry
[TRACE] missing plugins: 0
[DEBUG] cache hit: problems.json
[DEBUG] running leetcode.getProblem
[ERROR] failed to load locked problem! [0]

Environment

leetcode version returns 2.5.1

• leetcode-cli version:

• OS version:

redhat, not sure what version, it was working just a few days ago i think

• Node version:

v9.4.0

• Npm version:
  5.6.0

[skygragon]

@yuzhoul1991 Have you tried manually re-login?

[yuzhoul1991]

You mean leetcode user -l? If so yes I tried that Best, Yuzhou

…

On Mar 1, 2018, at 7:18 PM, skygragon ***@***.***> wrote: @yuzhoul1991 Have you tried manually re-login? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[skygragon]

There might be a bug if we have old problems.json cached, please try to clear the cache? I don't have premium account thus can't test it all.

leetcode cache -d problems

[15cm]

Same problem here. Even after clear the cache by leetcode cache -d.

[skygragon]

Sorry I can't debug this but I could give a hint that you might debug by yourself.

"failed to load locked problem" occurs in lib/plugins/leetcode.js:123, which implies "user.paid" is unexpectedly false.

123   if (problem.locked && !user.paid) return cb('failed to load locked problem!');

user.paid is assigned in lib/plugins/leetcode.js:95, which is extracted from the returned json of "https://leetcode.com/api/problems/$category/". For paid user, this "is_paid" field in json should be true (expected but not tested recently).

 76 plugin.getCategoryProblems = function(category, cb) {
 77   log.debug('running leetcode.getCategoryProblems: ' + category);
 78   const opts = makeOpts(config.sys.urls.problems.replace('$category', category));
 79
 80   spin.text = 'Downloading category ' + category;
 81   request(opts, function(e, resp, body) {
 82     e = checkError(e, resp, 200);
 83     if (e) return cb(e);
 84
 85     const json = JSON.parse(body);
 86
 87     // leetcode permits anonymous access to the problem list
 88     // while we require login first to make a better experience.
 89     if (json.user_name.length === 0) {
 90       log.debug('no user info in list response, maybe session expired...');
 91       return cb(session.errors.EXPIRED);
 92     }
 93
 94     const user = session.getUser();
 95     user.paid = json.is_paid;

I guess the latest json response has been changed recently that doesn't contain "is_paid" field anymore, which means we need seek other ways to detect paid user.

[15cm]

Maybe we can try to fetch the subscription state from leetcode.com/subscription/.

I currently delete lib/plugins/leetcode.js:123 as a temporary fix for myself.

[yunweiyuan]

Facing the same issue. But still cannot accessing the locked problem after deleting lib/plugins/leetcode.js:123, or manually setting user.paid to true.

[pengyu-hou]

I am running into the same issue as well. Tried upgrading to the latest version and deleting the cache. Nothing worked yet.

[yyang325]

Facing same error here.

[hankok]

Same

[skygragon]

@ALL feel free to try #96 to temporarily bypass the premium user check in leetcode-cli. I can't test it myself because I don't have a premium account...