Request timeout when attempting to download directly from Node

[rwader-swi]

Description:

• When it doesn't find the node in cache, it gives request timeout.
• After removing setup-node action, we've observed the github-scripts@v7 still run, but upload-artifacts action sometimes give issue.
• And sometimes there aren't any logs of setup-node, whether it is caching node or caching the action itself, or attempting to download directly. Hence, we aren't sure how to debug it. Seems like a cache issue to me because it happened after we re-deployed our self-hosted github runners.
• I tried to reproduce the issue by deleting the node cache in /opt/hostedtoolcache from our self-hosted runner, but in that case it passed 🙂
• Its very random. Please if anyone has any idea, or whether it's related to our network issue, then help us ASAP.

Action version:

setup-node@v4

node version: 20

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:
node-version: 20

Repro steps:

Expected behavior:
A description of what you expected to happen.

Actual behavior:
A description of what is actually happening.

[rwader-swi]

After tracing your code, the issue seems to have occurred at this step itself. Should I try giving a specific version like 20.x.x instead of just 20?

[rwader-swi]

https://nodejs.org/dist/index.json

[aparnajyothi-y]

Hello @rwader-swi, Thank you for creating this issue and we will look into it :)

[alirezaalavi87]

I get timeouts no matter what, can't download anything.

Attempting to download 14...
Request timeout: /repos/actions/node-versions/git/trees/main
Falling back to download directly from Node
::error::Request timeout: /dist/index.json

I can ping nodejs.org from the runner's server and curl https://nodejs.org/dist/index.json returns correct results so I don't think it is a network issue.

workflow.yaml

name: Build and Deploy Test Version

on:
  push:
    branches:
      - dev-branch

jobs:
  build_deploy:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v4
        with:
          ref: "dev-branch"
      - uses: actions/setup-node@v4
        with:
          node-version: 14
      - name: Install dependencies
        run: npm install
      - name: Build app
        run: npm run build
      - name: Deploy to server
        uses: appleboy/scp-action@master
        with:
          host: ${{ secrets.SERVER_HOST }}
          username: ${{ secrets.SERVER_USERNAME }}
          key: ${{ secrets.SSH_PRIVATE_KEY }}
          source: dist/
          target: /yacht/AppData/Config/Nginx/www/jtimar-lite/dist

[rwader-swi]

I can ping nodejs.org from the runner's server and curl https://nodejs.org/dist/index.json returns correct results so I don't think it is a network issue.

Yeah same in my case