-
Notifications
You must be signed in to change notification settings - Fork 88
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
Again sha256sum: WARNING as of today #118
Comments
Hi there, We have encountered this issue as well. -- Ivan @lifehome |
This could be a caching issue in our https://pkgs.tailscale.com CDN, we've restarted the edge nodes to flush the cache. |
Thanks @awly but I think we still not seeing 1.64.1 on pkgs.tailscale.com... EDIT: We have now rolledback to 1.64.0 for failover. -- Ivan @lifehome |
Hi there! I'm encountering this issue as well with latest TS version: 1.64.2.
|
Ahh, I see what's happening. So when the action runs SHA256SUM="$(curl -H user-agent:tailscale-github-action -L "${URL}.sha256")" It's getting a 500 response and curl -H user-agent:tailscale-github-action -L "$URL" -o tailscale.tgz --max-time 300 Gets a 404 response with body $ echo 'Not Found' | sha256sum
7515bf959b73b956ceb967351c7e299cbb3668a53d35f9c770eb72e00d93ced6 - For your actions, please use 1.64.0. |
Generally, you can see the latest available Linux version at https://pkgs.tailscale.com/stable/#static. As of today, Github releases are not the most accurate way to find latest available versions for all platforms. |
If package or SHA download from pkgs.tailscale.com fails with a non-200 repsonse code, make the whole action fail. This catches things like incorrect versions. Updates #118
If package or SHA download from pkgs.tailscale.com fails with a non-200 repsonse code, make the whole action fail. This catches things like incorrect versions. Updates #118
If package or SHA download from pkgs.tailscale.com fails with a non-200 repsonse code, make the whole action fail. This catches things like incorrect versions. Updates #118
OK, this should now fail slightly more obviously with |
Hit these today and a couple of weeks ago again...
#88
#89
version is set to latest in the GH action.
The text was updated successfully, but these errors were encountered: