Canary binary is missing

[willemneal]

Currently get the following CI error:

curl: (22) The requested URL returned error: 404 
Binary download from https://nodejs.org/download/v8-canary//v14.0.0-v8-canary2019120435eb057712/node-v14.0.0-v8-canary2019120435eb057712-linux-x64.tar.xz failed, trying source.
grep: /home/runner/.nvm/.cache/bin/node-v14.0.0-v8-canary2019120435eb057712-linux-x64/node-v14.0.0-v8-canary2019120435eb057712-linux-x64.tar.xz: No such file or directory
Provided file to checksum does not exist.
Binary download failed, trying source.
/home/runner/work/_actions/dcodeIO/setup-node-nvm/v1.0.0/index.js:16
  if (code !== 0) throw Error("installation failed with " + code);
                  ^

Error: installation failed with 1
    at ChildProcess.<anonymous> (/home/runner/work/_actions/dcodeIO/setup-node-nvm/v1.0.0/index.js:16:25)
    at ChildProcess.emit (events.js:200:13)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)

Where do I update the url to the binary?

[dcodeIO]

There are some binaries but not others it seems. Wondering if it is still building or failed. Suggesting to ignore the canary build for now.

To answer the question: This is what CI currently does, that is set the mirror and install node, which is the latest canary automatically. As long as we want latest, there is not much we can reasonably do but wait.

[dcodeIO]

Looks like they have issues.

[willemneal]

Okay cool thanks!

[dcodeIO]

The issues appear like those might take a while to resolve, so perhaps pinning to v14.0.0-v8-canary201911242015a12d82 is indeed an option? Hmm

[MaxGraey]

I guess pinning for now is better then completely disable

[MaxGraey]

Solved in #990