handle expired leetcode session error #72
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e session variable has expired. Provides helpful message instead of throwing type error on next line
nirav-v
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I ran into an issue where the github action stopped working after some time and was giving me this error:
TypeError: response.data.data.submissionList.submissions is not iterableAfter debugging, the cause was that my leetcode session had expired causing the submissions to be null. I have added a check against this case that will show an error message instead attempting to iterate over null submissions. Workflow should now show a message telling the user their session may have expired if no submissions are being returned from the leetcode api, rather than throwing the previous type error.