-
Notifications
You must be signed in to change notification settings - Fork 212
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
It's trying to download a very old artifact, when much newer ones exist #240
Comments
An update: I copied the code for this action into my project, and added some |
If anyone needs a script to workaround this issue take a look at firezone/firezone#2665 |
thank's a lot. |
I'm using this YAML:
And getting this result:
The thing is, there are many dozens of newer runs! (Maybe even hundreds? Godot is a very active project.)
My first thought was that maybe the API is returning them in chronological order and picking the first (and hence oldest) one. So, I tried recreating the API calls I see in main.js using curl on the command-line, but it appears that the API is correctly returning them in reverse chronologic order (ie. newest first).
When I try to list the runs:
Here's just the first one (out of apparently 52,727 of them :-)):
If it would pick that one, that'd be fabulous!
Since I'm using
search_artifacts
andcheck_artifacts
, I also tried listing the artifacts for this run:And I can see an artifact with the correct name in there:
What can I do to induce it to try and download this artifact?
Looking at the code in main.js, I'm not seeing anything obviously wrong, unless the GitHub client is doing something to sort the results in chronological order (such that the oldest is first)?
Thanks!
The text was updated successfully, but these errors were encountered: