Skip to content

"leetcode test" doesn't work anymore #192

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

Open
htang2023 opened this issue Nov 5, 2019 · 1 comment · May be fixed by #214
Open

"leetcode test" doesn't work anymore #192

htang2023 opened this issue Nov 5, 2019 · 1 comment · May be fixed by #214

Comments

@htang2023
Copy link

htang2023 commented Nov 5, 2019

"leetcode test" stuck in "Waiting for judge result".

How to reproduce

leetcode test 1.two-sum

Stuck in "Waiting for judge result"
-->

Environment

  • leetcode-cli version: 2.6.2
  • OS version: win10
  • Node version: v12.13.0
  • Npm version: 6.12.0
@advpetc
Copy link

advpetc commented Nov 20, 2019

on mac os:
$ npm -g uninstall leetcode-cli --save
$ npm -g install leetcode-tools/leetcode-cli

HwangTaehyun added a commit to HwangTaehyun/leetcode-cli that referenced this issue Jun 28, 2020
- Bug fix for test command freezing issue
  - There seems to have been some changes in response for leetcode test api.
    - leetcode test url's response doesn't have "interpret_expected_id"
    - leetcode verify url's response have test's expected results (ex. expected answer)
@HwangTaehyun HwangTaehyun linked a pull request Jun 28, 2020 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants