I was doing a dynamic programming problem in Python, and without thinking too much about it provided recursive code for the solution. When I ran leetcode-submit for the problem I never got anything back in the result buffer at all - no messages of any kind.
After a bit of digging it turned out that the solution failed on one of the tests because it hit the Python recursion depth limit, which manifests itself in the LeetCode API as status_code of 12 and status_msg of "Memory Limit Exceeded". However, it looks like the code in leetcode--show-submission-result doesn't handle this case at all - it simply swallows it.
I suggest that status_code: 12 be handled like the rest - with a report of what failed and the current test case. I'll submit a PR shortly to provide some useful status for this case - pretty much in parallel to the existing "Time Limit Exceeded" error.
I was doing a dynamic programming problem in Python, and without thinking too much about it provided recursive code for the solution. When I ran
leetcode-submitfor the problem I never got anything back in the result buffer at all - no messages of any kind.After a bit of digging it turned out that the solution failed on one of the tests because it hit the Python recursion depth limit, which manifests itself in the LeetCode API as
status_codeof 12 andstatus_msgof "Memory Limit Exceeded". However, it looks like the code inleetcode--show-submission-resultdoesn't handle this case at all - it simply swallows it.I suggest that
status_code: 12be handled like the rest - with a report of what failed and the current test case. I'll submit a PR shortly to provide some useful status for this case - pretty much in parallel to the existing "Time Limit Exceeded" error.