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

Retry support #3

Closed
isage opened this issue Dec 28, 2022 · 10 comments
Closed

Retry support #3

isage opened this issue Dec 28, 2022 · 10 comments
Assignees

Comments

@isage
Copy link

isage commented Dec 28, 2022

Github likes to throw ECONNRESET sometimes, so it would be good to have retry support.
See svenstaro#62

@thunder-coding
Copy link
Member

thunder-coding commented Dec 28, 2022

I don't see any of those errors in https://ithub.com/termux/termux-packages. (The only place which I monitor and know uses this action). Can you share a recent action run which was stopped due to this error?

Also for such network error and similar, I'll have to look into what specific error is raised so as to target that only instead of also catching all sorts of errors. The documentation does not seem t be very specific about this though

EDIT: Just found https://github.com/octokit/plugin-retry.js Probably that's what I need to set up.

@thunder-coding thunder-coding self-assigned this Dec 28, 2022
@isage
Copy link
Author

isage commented Dec 28, 2022

We're having it sometimes with svenstaro action (we're currently looking where to migrate from it)
But it isn't really descriptive https://github.com/vitasdk/packages/actions/runs/3792125068/jobs/6448313436

@thunder-coding
Copy link
Member

It seems like the error is very consistent when uploading lots of files. I grepped through all the source (including node_modules) for the latest release of this repository (I'm talking about this fork) for "Server Error". Did not find any exact string that matches the error. Can you try switching to this action, in case it does make any difference? Maybe the error message may change and can help

@isage
Copy link
Author

isage commented Dec 28, 2022

Yeah, sure.
vitasdk/packages#251 as soon as this merged.
We also sometimes hit api rate limit with artifacts upload, which is strange, sine with token it should be 5000 and is more that enough for whole workflow. So some kind of descriptive error (or dumping response headers) would be nice too, to allow to debug such cases.

@isage
Copy link
Author

isage commented Dec 29, 2022

Huh. So, https://github.com/isage/packages/actions/runs/3799384974
it hits api rate limit. Yet, available calls before action is

"core": {
      "limit": 1000,
      "used": 48,
      "remaining": 952,
      "reset": 1672308195
    },

EDIT: i'll move api rate discussion to #5

@isage
Copy link
Author

isage commented Dec 31, 2022

Ok, looks like we got ECONNRESET https://github.com/vitasdk/packages/actions/runs/3812070202/jobs/6485261991
Or maybe something else, since it's hard to tell from Error: Server Error

@thunder-coding
Copy link
Member

Ok, looks like we got ECONNRESET https://github.com/vitasdk/packages/actions/runs/3812070202/jobs/6485261991
Or maybe something else, since it's hard to tell from Error: Server Error

Can you try enabling debug logging for GitHub Actions. See https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging. Hope it helps find the actual problem.

@isage
Copy link
Author

isage commented Dec 31, 2022

I don't have required access, but i've asked maintainer to do so

@isage
Copy link
Author

isage commented Jan 11, 2023

https://github.com/vitasdk/packages/actions/runs/3895533347/jobs/6651429809
this is strange, it's still just says "Server error" even with debug.

@isage
Copy link
Author

isage commented May 24, 2023

Haven't had that issue for a long time now, so i'll close for now

@isage isage closed this as completed May 24, 2023
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

2 participants