Skip to content
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

Error: Request failed with status code 500 #29

Open
yyang2018mel opened this issue Dec 28, 2022 · 5 comments
Open

Error: Request failed with status code 500 #29

yyang2018mel opened this issue Dec 28, 2022 · 5 comments

Comments

@yyang2018mel
Copy link

I used to run the action successfully. but recently I always get this error.

[Wed, 28 Dec 2022 10:29:13 GMT] Getting submission from LeetCode, offset 0
[Wed, 28 Dec 2022 10:29:14 GMT] Getting submission from LeetCode, offset 20
[Wed, 28 Dec 2022 10:29:16 GMT] Error fetching submissions, retrying in 1 seconds...
[Wed, 28 Dec 2022 10:29:17 GMT] Error fetching submissions, retrying in 3 seconds...
[Wed, 28 Dec 2022 10:29:21 GMT] Error fetching submissions, retrying in 9 seconds...
[Wed, 28 Dec 2022 10:29:31 GMT] Error fetching submissions, retrying in 27 seconds...
[Wed, 28 Dec 2022 10:29:59 GMT] Error fetching submissions, retrying in 81 seconds...
[Wed, 28 Dec 2022 10:31:21 GMT] Error: Request failed with status code 500
at createError (/home/runner/work/_actions/joshcai/leetcode-sync/v1.5/node_modules/axios/lib/core/createError.js:16:15)
at settle (/home/runner/work/_actions/joshcai/leetcode-sync/v1.5/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/home/runner/work/_actions/joshcai/leetcode-sync/v1.5/node_modules/axios/lib/adapters/http.js:269:11)
at IncomingMessage.emit (node:events:402:35)
at endReadableNT (node:internal/streams/readable:1343:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
Error: Error: Request failed with status code 500

@Suvraneel
Copy link

Suvraneel commented Jan 4, 2023

@joshcai +1 to this
I found & tried this out for the 1st time today...
Workflow Run here

image

@joshcai
Copy link
Owner

joshcai commented Jan 5, 2023

Thanks for the reports, does look like a bug. Do you know if it fails deterministically with the same offset numbers? I'm wondering if the final fetch is the issue or if it's some kind of flakiness.

I wasn't able to reproduce yet, but I'll try to look at this more over the weekend when I get back home from the holidays. Sorry for the inconvenience!

@MahmoudAbdullah99
Copy link

I had the same problem
image

@joshcai
Copy link
Owner

joshcai commented Jan 9, 2023

Hmm I still wasn't able to reproduce this and had a successful run recently, do any of you guys mind sharing info on how to reproduce? e.g. potentially sending your LeetCode credentials privately to see if it's related to the LeetCode account?

@MahmoudAbdullah99
Copy link

Of course, how can I reach you?

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

No branches or pull requests

4 participants