-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
.gz is not a supported archive file format error on Windows with new version 9c1e94e0 #1721
Comments
In 9c1e94e, on line 7098 of Taking a step back, I'm curious why a tarball was downloaded in the first place. It looks like a zipball should be downloaded, when running on Windows. Perhaps the issue lies there. |
I got this error too. Do we have any alternatives? |
I have this issue too. Downgrading to v3 works. |
Also seeing this issue, explictly using v4.1.4 resolves the issue for now. |
Same problem... also fixed by |
I reverted |
I'm not actually sure if it's a tarball. On Windows we should be using checkout/src/github-api-helper.ts Lines 134 to 136 in 44c2b7a
The problem may come from the fact that the file extension was hardcoded: checkout/src/github-api-helper.ts Line 38 in 44c2b7a
This combined with updating the It seems like If that's the case, it should be as simple as main...users/cory-miller/windows-test to fix. I don't have easy access to a Windows machine where |
@cory-miller Will you be submitting that PR soon? Is it waiting on a review or testing? |
@tehpsalmist delay was due to needing but not having a Windows machine without Git.exe handy. I was able to set one up and tested the change. PR is up now. |
I've created https://github.com/actions/checkout/releases/tag/v4.1.6 and cannot reproduce this issue on that tag. I'm going to do some additional testing before promoting that to v4 (I'll do that on Monday). Feel free to try against |
I testing v4.1.6 in the same environment in which I first observed this issue. With v4.1.6, the file is a zip and the extract is successful:
Looks good, thanks! |
|
Previously (at version 0ad4b8f), it would generate this extract command, which works properly:
Now at 9c1e94e, it generates this command, which fails:
The text was updated successfully, but these errors were encountered: