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

Latest version number and proper failure is not guaranteed #1

Closed
ghost opened this issue Mar 24, 2022 · 5 comments
Closed

Latest version number and proper failure is not guaranteed #1

ghost opened this issue Mar 24, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@ghost
Copy link

ghost commented Mar 24, 2022

One of our workflow run failed with the following error:

[ERROR] CUID#7 - Download aborted. URI=https://github.com/rclone/rclone/releases/download/null/rclone-null-osx-amd64.zip
Exception: [AbstractCommand.cc:351] errorCode=3 URI=https://github.com/rclone/rclone/releases/download/null/rclone-null-osx-amd64.zip
-> [HttpSkipResponseCommand.cc:219] errorCode=3 Resource not found

It seems to be that the error came from here, where for some reason the latest version was determined as null:

version=$(curl -s https://api.github.com/repos/rclone/rclone/releases/latest | jq -r '.tag_name')

Maybe some additional check/retry logic could be implemented in case the version is not properly returned, to make the run more resilient.

This step also didn't fail (which it should have), even though it failed to install the tool. Additional check could be implemented for that too.

@ghost ghost changed the title Latest version number is not guaranteed Latest version number and proper failure is not guaranteed Mar 24, 2022
@AnimMouse AnimMouse added the bug Something isn't working label Mar 24, 2022
@AnimMouse
Copy link
Owner

It seems to be that the error came from here, where for some reason the latest version was determined as null:
Maybe some additional check/retry logic could be implemented in case the version is not properly returned, to make the run more resilient.

It seems like GitHub APIs goes down recently, I think if GitHub API goes down, then perhaps we shouldn't be using GitHub Actions, right?

This step also didn't fail (which it should have), even though it failed to install the tool. Additional check could be implemented for that too.

Thanks for reporting that bug, it seems like I forgot to add set -e in the script.

@ghost
Copy link
Author

ghost commented Mar 24, 2022

It seems like GitHub APIs goes down recently, I think if GitHub API goes down, then perhaps we shouldn't be using GitHub Actions, right?

Yes, I haven't mentioned it, but the issue happened at 22:35 UTC, and the outage finished at 17:40 UTC, so GitHub was officially fully functional.

@AnimMouse
Copy link
Owner

AnimMouse commented Mar 28, 2022

the issue happened at 22:35 UTC, and the outage finished at 17:40 UTC, so GitHub was officially fully functional.

With the recent incident on GitHub 3 days in a row due to their mySQL1 load, I think GitHub is still down during that time.

Update: I was wrong. #3

This bug has been solved on 6e5a0cb, and this action will now fail when it failed to install the tool. Thanks for your bug report.

@ghost
Copy link
Author

ghost commented Mar 28, 2022

Thank you as well!

@AnimMouse
Copy link
Owner

where for some reason the latest version was determined as null

#3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant