-
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
Assumption of having a .zip file for an artifact could be "wrong" #92
Comments
@yarikoptic The documentation all but explicitly states that artifacts are downloaded as zips. I think this was just a temporary fluke on GitHub's part. |
not too long after the gateway error out, got another errorred out run
so even if doc says one thing, clearly something else might be happening and we should figure out what leads to it (may be some html with error returned) and might just need to retry |
Let's handle that fluke programmatically -- sleep some and retry. I don't have a good clue on how long/many -- probably up to 5 stretching to a few minutes |
Retry downloads of invalid zipfiles
I wonder if it was some json or HTML telling us something about anything? I have not looked at the code if we guard there for return codes (may be was one of the timeouts or smth). If there is no guard -- should be added along with a retry
Seems to not happen frequently, but also the removal of the file (I guess it was removed) forbids any introspection - may be some information could be provided there about the file (e.g. file size and may be even content if file e.g. < 10k in size?) before it gets purged?
edit: upon rerun tinuous happily fetched it:
tinuous 0.2.0+54.g0f13cf6
The text was updated successfully, but these errors were encountered: