-
Notifications
You must be signed in to change notification settings - Fork 4
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
Sleep/retry on 502 Bad Gateway #129
Comments
@yarikoptic A 502 at that location should have been retried unless the maximum number of retries (10) had already been reached. Is the traceback preceded by a bunch of warning messages of the form "Request to %s returned %d; waiting & retrying"? |
Sorry for the noise - I guess I was blind, indeed it did retries for 6 minutes:
not sure if extending it would be productive... Let's assume it was a fluke |
Received similar fail in dandi-api and when I clicked on the url in a phone browser got {
"message": "Must have admin rights to Repository.",
"documentation_url": "https://docs.github.com/rest/reference/actions#download-workflow-run-logs"
} so may be there is more to this story... logs etc from the run2021-08-10T18:10:03-0400 [INFO ] tinuous Downloading logs for cli-integration.yml (Test Integration with dandi-cli) #450 to 2021/08/10/github/pr/470/b923159/cli-integration.yml/450-success |
@yarikoptic Accessing GitHub Actions logs via the API requires a token with admin permissions for the repository in question, which any standard personal token should have (assuming the user in question is an admin for the repo). The message you saw is really irrelevent to any server errors that may be occurring on GitHub's end. |
ok, fluke it is I guess |
Fresh cron run on smaug for datalad (
Cron <datalad@smaug> chronic flock -n -E 0 /home/datalad/.run/tinuous-datalad.lock /mnt/datasets/datalad/ci/logs/tools/cron_job
) hadI would assume that it was some intermittent issue and sleep/retry should be sufficient to address it.
I checked mail -- it was the first and only so far incident of this kind. Although seems to be rare, IMHO still worth accounting for
The text was updated successfully, but these errors were encountered: