Downloading from nodejs.org failing

[paglias]

I'm not sure this is the best repo to report the issue, if it's the wrong place please close this :)

We've been using Github Actions successfully for a few days but starting today all our builds have started to fail at the setup-node step with this error:

4m 57s
##[error]Node run failed with exit code 1
Run actions/setup-node@v1
  with:
    node-version: 12.x
    always-auth: false
/bin/tar xzC /home/runner/work/_temp/83341e1a-c86d-4ddb-9963-ef01607f6e1e -f /home/runner/work/_temp/58fc8365-fe95-474e-ad3c-c5511594abdd

gzip: stdin: unexpected end of file
/bin/tar: Unexpected EOF in archive
/bin/tar: Unexpected EOF in archive
/bin/tar: Error is not recoverable: exiting now
##[error]The process '/bin/tar' failed with exit code 2
##[error]Node run failed with exit code 1

Attaching a screenshot for more clarity

You can see an example of a failed build here https://github.com/HabitRPG/habitica/pull/11474/checks?check_run_id=271716057.

The code of the workflow is the standard one that can be seen in the official docs

steps:
.....
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v1
      with:
        node-version: ${{ matrix.node-version }}
....

[rashedmyt]

I am also having the same issue

[m4rkmckenna]

Same issue on ubuntu-latest

[chingc]

I'm also having the same problem. One thing I noticed on my CircleCI builds is nvm is failing to download nodejs. The download is so slow that it will timeout, then the installation fails due to an incomplete download.

I'm think it might be a similar problem affecting this action. If it's the same issue, it would be nice if there was some kind of automatic resume so it doesn't keep trying to download from the beginning.

[abatilo]

I'm having the same problem!

[dijam]

I retied couple of times. Waited 10 min, a cup of coffee, tried again and it worked.

[ronaldtse]

Same issue, retried couple of times but still didn't work. https://github.com/metanorma/isodoc/runs/271773491

Seems like an issue from upstream, but could this action use locally installed Node.js?

GHA help says that Node.js 10.16 is installed on Ubuntu 16.04 and 18.04.

[vibou]

Same here ! What's going on !

[timofeee]

Just experimenting right now with Actions, good to know it's not something I messed up

[nicubarbaros]

Same here! With node 8.15.

[andrew-boyd]

Possibly related to widespread DNS issues from AWS?

[simon300000]

Having problem with node 12 ubuntu-latest

[nicubarbaros]

Suddenly completed after rerunning the same action couple of times

[vibou]

Suddenly completed after rerunning the same action couple of times

Did you run the action with the re-run check or you trigger the workflow with an event ?

[panva]

dtto, only a different error.

[dmail]

I encountered a 500 error once too, maybe unrelated.

[panva]

I encountered a 500 error once too, maybe unrelated.

saw that too

[tunnckoCore]

Nope. It's because of the action, I'm sure.

Same here.

[simon300000]

I just noticed node published v13 yesterday, might it be related?

[panva]

I just noticed node published v13 yesterday, might it be related?

No, i had node 13 builds running fine 7 hours ago.

[chingc]

It's a download issue. Node is failing to download which causes tar or 7z to fail when trying to extract.

See this issue: nodejs/build#1993

[nicubarbaros]

Did you run the action with the re-run check or you trigger the workflow with an event ?

Rerun check

[tunnckoCore]

It's working for couple of hours already.

[rigobcastro]

Same issue here

[edward-soetiono-asto]

lost so many hours from this error

any alternative?

[tunnckoCore]

as I understand it's upstream, so...

[bryanmacfarlane]

UPDATE:

Yes, it's external and nodejs downloads (not a CDN) is having. This action just downloads from their endpoint.

nodejs/build#1993

We do have a workitem to cache the latest of each major version on our hosted images and this action checks that cache first (resolved the semver you supply against the cache and if not there queries the cloud).

Downside is you may not get absolute latest (image gen'd yesterday, patch released today). but we have a plan for that as well - an option in the action to always query for cloud first.

You could also fall back on failure the only issue with that takes a long time every invocation when an issue like this is happening and it's a fresh machine every time.

Thoughts?

[chingc]

@bryanmacfarlane I think adding automatic resume to interrupted downloads would be great too. From what I can tell, the file IS being downloaded but it's so slow it can't finish before timing out.

[neo]

I think having a cached version in the image would definitely help!

[lol768]

Just ran into this today - would also appreciate a cache service.

[blane1988]

Same. The past hour has seen many failures for the Node action. Some jobs it will work, but most don't.

[Avinger27]

Running into this today. is anyone still facing this issue?

[blane1988]

@Avinger27 It is running fine for me. Are you still facing the issue?

[daiky00]

I just ran into this issue today

[Etherdaemon]

Facing this issue today on Azure DevOps - I've had 1 build go past the nodeTool install successfully out of 8 so far.

[ssannidhi-palo]

Facing this issue today on github actions, with ubuntu-18.04 and node 12.14

test:
runs-on: ubuntu-18.04
name: Run unit & integration tests
steps:
- uses: actions/checkout@v1
- name: Setup Node.js
uses: actions/setup-node@v1
with:
node-version: 12.14

[kitmoovup]

Same issue.

[Kostanos]

the similar issue maybe?

[gustavlindstroms]

My issue might be realated

[dmitry-shibanov]

Hello everyone. We released tag v2 for setup-node. It should resolve some issues related downloading. For details you can take a look on this comment and issue.
For now I'm closing the issue. If you have any concerns feel free to ping us.