Can't use 'tar -xzf' extract archive file

[szepeviktor]

Download action repository 'actions/checkout@v3' (SHA:f43a0e5ff2bd294095638e18286ca9a3d1956744)
Error: Can't use 'tar -xzf' extract archive file: /home/runner/work/_actions/_temp_81e514cc-59b2-4af3-aa4d-6f8210ffde88/752d468e-f00d-474c-af3f-80fbe27b5318.tar.gz. return code: 2.

That hash points to v3.6.0

I do not know what to add here.
https://github.com/nunomaduro/larastan/actions/runs/6074130772/job/16477441571

[shapirus]

It looks like it affects multiple (to say the least) users :)

For a workaround, is anyone aware how to pin version used in a workflow to an earlier release?

up: I too can confirm that changing to checkout@v4 works.

[jamesmhaley]

Does this have anything to do with the v4.0 release from @takost & @simonbaird?

[kevinlul]

Seems to be a transient network-related issue, based on previous instances.

#514 #545 #672 #673 #815 #948 #949

[mvdan]

I'm trying to think how this even broke. It must have been on the server side, because we are using actions/checkout@v3, so we should not be affected by the recent v4.0.0 tag.

[ovr]

actions/checkout@v4 - v4 works. It can be used as a quick fix.

[kevinlul]

The second re-run (third attempt) worked for me: https://github.com/DawnbrandBots/bastion-bot/actions/runs/6074117346
I think it's not related to specifically this repository but with GitHub itself serving the tarball.

[mvdan]

Seems to be a transient network-related issue, based on previous instances.

Interesting - network reliability aside, I wonder why actions/checkout isn't retrying on network errors.

[andraspatka-dev]

Confirmed, updating to v4 fixes the issue.

[pimhakkertgc]

Oh no... We need this to work today :#

EDIT: No I cannot just change to v4 for a production environment that needs to go live soon.

[kevinlul]

Interesting - network reliability aside, I wonder why actions/checkout isn't retrying on network errors.

It's not actions/checkout — it's the Actions runner itself downloading and extracting all the used action packages before starting the workflow.

[msandu62]

same issue here

[robmaxwellirl]

Seems like it's back working for me now anyways.