-
Notifications
You must be signed in to change notification settings - Fork 75
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
Action does not download package - fails with "gzip: stdin: not in gzip format" error #89
Comments
I want to fix it with using github cache #87, so after one run it should work. |
no problem - we will update to version 2 if needed. |
@GalOzRlz please have a look at my PR. it works for me, but I am new to GH Actions, so YMMV |
I suspect this may have been related to #88, as the error responses would not have been gzipped. |
This is happening again today! |
@beaugunderson @GalOzRlz |
We fix the version to version: 1.30.0 --
|
1.24.2 for us (for no special reason, I assume we could upgrade to
something more recent without major issues if it would help)
…On Tue, Oct 03, 2023 at 11:06 PM, Denton Gentry ***@***.***> wrote:
@beaugunderson <https://github.com/beaugunderson> What tailscale version
is it trying to download? The v2 action defaults to 1.42.0, is that it or
do you set version ?
—
Reply to this email directly, view it on GitHub
<#89 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPCX5GLQ36R3UF5P32V7DX5T4IDAVCNFSM6AAAAAA4CZYL5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWGE4TINJVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
At this point I don't think a version change would help. We're focussing on the pkgs server and the CDN in front of it, which is used for all Tailscale versions. |
Thanks @DentonGentry , much appreciated |
It isn't failing everywhere:
A workflow using this GitHub Action passed here a few minutes ago: https://github.com/tailscale/github-action/actions/runs/6403096635/job/17380921729?pr=91 I suppose a problem in the CDN serving pkgs.tailscale.com might only manifest in GitHub datacenters other than the one we used for that run. However it looks like all GitHub Actions still run in the US, and the CDN doesn't have a huge number of different regional nodes. For anyone experiencing trouble today: are you self-hosting runners? |
at the moment we’re seeing majority pass,
maybe 20-30% fail
…On Wed, Oct 4 2023 at 01:05, Denton Gentry ***@***.***> wrote:
It isn't failing everywhere:
$ curl -H user-agent:tailscale-github-action -L https://pkgs.tailscale.com/stable/tailscale_1.24.2_amd64.tgz --output /tmp/tailscale_1.24.2_amd64.tgz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 81 100 81 0 0 194 0 --:--:-- --:--:-- --:--:-- 195
100 18.2M 100 18.2M 0 0 16.6M 0 0:00:01 0:00:01 --:--:-- 41.9M
$ curl -H user-agent:tailscale-github-action -L https://pkgs.tailscale.com/stable/tailscale_1.24.2_amd64.tgz.sha256
a25bba595af9a67fa2b3ef7df5f92b343179470b14115c76fd2f6e92cc3bc9ac <https://pkgs.tailscale.com/stable/tailscale_1.24.2_amd64.tgz.sha256a25bba595af9a67fa2b3ef7df5f92b343179470b14115c76fd2f6e92cc3bc9ac>
$ echo "a25bba595af9a67fa2b3ef7df5f92b343179470b14115c76fd2f6e92cc3bc9ac /tmp/tailscale_1.24.2_amd64.tgz" | sha256sum -c
/tmp/tailscale_1.24.2_amd64.tgz: OK
$ curl -H user-agent:tailscale-github-action -L https://pkgs.tailscale.com/stable/tailscale_1.30.0_amd64.tgz --output /tmp/tailscale_1.30.0_amd64.tgz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 81 100 81 0 0 188 0 --:--:-- --:--:-- --:--:-- 188
100 19.5M 100 19.5M 0 0 17.0M 0 0:00:01 0:00:01 --:--:-- 17.0M
$ curl -H user-agent:tailscale-github-action -L https://pkgs.tailscale.com/stable/tailscale_1.30.0_amd64.tgz.sha256
8660387a79d539838f032e0cbe620cb241ee3f0636fd8942275d37ca38f456fd <https://pkgs.tailscale.com/stable/tailscale_1.30.0_amd64.tgz.sha2568660387a79d539838f032e0cbe620cb241ee3f0636fd8942275d37ca38f456fd>
$ echo "8660387a79d539838f032e0cbe620cb241ee3f0636fd8942275d37ca38f456fd /tmp/tailscale_1.30.0_amd64.tgz" | sha256sum -c
/tmp/tailscale_1.30.0_amd64.tgz: OK
A workflow using this GitHub Action passed here a few minutes ago:
https://github.com/tailscale/github-action/actions/runs/6403096635/job/17380921729?pr=91
------------------------------
I suppose a problem in the CDN serving pkgs.tailscale.com might only
manifest in GitHub datacenters other than the one we used for that run.
However it looks like all GitHub Actions still run in the US
<community/community#11727>, and the CDN
doesn't have a huge number of different regional nodes.
For anyone experiencing trouble today: are you self-hosting runners?
—
Reply to this email directly, view it on GitHub
<#89 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPCXZHYJDWB4CU4FBQAM3X5UKGNAVCNFSM6AAAAAA4CZYL5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWGM2TCNRQGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No self running hosts in these workflows |
any news here? we're still seeing lots of failures |
fwiw 1.48.2 is installing for us with no failures yet! |
Updates #89 Signed-off-by: Denton Gentry <dgentry@tailscale.com>
@beaugunderson 1.24.2 gets a checksum error and 1.48.2 does not? |
@DentonGentry zero failures out of ~60 after switching to 1.48.2 👍 |
Updates #89 Signed-off-by: Denton Gentry <dgentry@tailscale.com>
If someone who can reproduce the issue is willing to run the action @a5ed86cd4900e943e2aa3f760fd8472f04e46469 instead of v2, it will output the expected and actual checksums to get an idea what is happening. |
I'm going to try and make this happen and get back to you |
still using version: 1.30.0 btw |
It got the redirect to the CDN, then downloaded 19 bytes and stopped. |
|
Yep just 1.30.0
We're in Israel. |
Getting the same. Version: 1.36.0 |
I think we've worked out the series of issues starting from a data consistency problem in a provider's tools, which led to not deploying updates to two of the nodes in our infrastructure, which led to a 404 for those unfortunate enough to hit one of those nodes. We think this is resolved now. If you see checksum errors occurring after 5:30pm Pacific time on October 5, please update this issue. |
We also added metrics for this specific issue, and have seen no occurrences since October 5. I'm going to close this as resolved. For people reading this in the future, if you see "gzip: stdin: not in gzip format" or a checksum error please do not comment on this issue or reopen it. This one is fixed. If you encounter a new problem, even with the same symptom, please open a new bug. |
For more than 24 hours our action is failing from time to time with this error - it looks like it won't download the package. Is this a CDN issue on the servers?
The text was updated successfully, but these errors were encountered: