-
Notifications
You must be signed in to change notification settings - Fork 652
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
Cannot show output when the answer is wrong #414
Cannot show output when the answer is wrong #414
Comments
What if you remove the folder |
Encountered the same problem. Reinstall does not solve the problem. |
Could you provide the following information to help me diagnostic:
|
Sure.
|
Actually..... it no longer repros tonight...the issue is gone... Thanks |
I can repro it now. It happens when the answer is wrong. Will fix it in the cli side. |
🐛 Bug Report
Cannot submit
To Reproduce
Sign in and then submit a solution
Expected behavior
was working yesterday. But hit this exception tonight.
Extension Output
c:\Users\haoxu.vscode\extensions\shengchen.vscode-leetcode-0.15.3\node_modules\vsc-leetcode-cli\lib\plugins\leetcode.js:267
x.stdout = util.inspect((result.code_output || []).join('\n'));
^
TypeError: (result.code_output || []).join is not a function
at formatResult (c:\Users\xxx.vscode\extensions\shengchen.vscode-leetcode-0.15.3\node_modules\vsc-leetcode-cli\lib\plugins\leetcode.js:267:56)
at Request._callback (c:\Users\xxx.vscode\extensions\shengchen.vscode-leetcode-0.15.3\node_modules\vsc-leetcode-cli\lib\plugins\leetcode.js:232:16)
at Request.self.callback (c:\Users\xxx.vscode\extensions\shengchen.vscode-leetcode-0.15.3\node_modules\request\request.js:185:22)
at Request.emit (events.js:189:13)
at Request. (c:\Users\xxx.vscode\extensions\shengchen.vscode-leetcode-0.15.3\node_modules\request\request.js:1161:10)
at Request.emit (events.js:189:13)
at IncomingMessage. (c:\Users\xxx.vscode\extensions\shengchen.vscode-leetcode-0.15.3\node_modules\request\request.js:1083:12)
at Object.onceWrapper (events.js:277:13)
at IncomingMessage.emit (events.js:194:15)
at endReadableNT (_stream_readable.js:1125:12)
Your Environment
The text was updated successfully, but these errors were encountered: