2 years ago
This build has been working correctly until yesterday.
Then i noticed this was the issue via logs
11 9.468 …/canvas@2.11.2/node_modules/canvas install: (Use node --trace-deprecation ... to show where the warning was created)
11 9.469 …/canvas@2.11.2/node_modules/canvas install: node-pre-gyp http GET https://github.com/Automattic/node-canvas/releases/download/v2.11.2/canvas-v2.11.2-node-v127-linux-glibc-x64.tar.gz
11 9.688 …/canvas@2.11.2/node_modules/canvas install: node-pre-gyp ERR! install response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.11.2/canvas-v2.11.2-node-v127-linux-glibc-x64.tar.gz
11 9.689 …/canvas@2.11.2/node_modules/canvas install: node-pre-gyp WARN Pre-built binaries not installable for canvas@2.11.2 and node@22.2.0 (node-v127 ABI, glibc) (falling back to source compile with node-gyp)
11 9.689 …/canvas@2.11.2/node_modules/canvas install: node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.11.2/canvas-v2.11.2-node-v127-linux-glibc-x64.tar.gz
This is what the old logs look like
11 10.02 …/canvas@2.11.2/node_modules/canvas install: (node:87) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
11 10.02 …/canvas@2.11.2/node_modules/canvas install: (Use node --trace-deprecation ... to show where the warning was created)
11 10.02 …/canvas@2.11.2/node_modules/canvas install: node-pre-gyp http GET https://github.com/Automattic/node-canvas/releases/download/v2.11.2/canvas-v2.11.2-node-v120-linux-glibc-x64.tar.gz
11 10.41 …/canvas@2.11.2/node_modules/canvas install: node-pre-gyp info install unpacking Release/
11 10.42 …/canvas@2.11.2/node_modules/canvas install: node-pre-gyp info install unpacking Release/libgobject-2.0.so.0
11 10.48 …/canvas@2.11.2/node_modules/canvas install: node-pre-gyp info install unpacking Release/libstdc++.so.6
You can see the links are different
ⓘ Deployment information is only viewable by project members and Railway employees.
4 Replies
2 years ago
the suggested solution about adding python to provides does NOT work.
2 years ago
I found out its an issue with node 22 i have to make use it used nothing greater than node 21 to build and it worked.
Previous builds had always been using node 21 so it just made sense
2 years ago
Node 22 support was recently added to nixpacks so if you had your engines.node set to something like >=18 the latest is going to be used, I would recommend setting it to a fixed version if thats not something you haven't done already.
Status changed to Solved Railway • over 1 year ago
2 years ago
using a fixed node versions fixes the problem