please let me know what someone from railway is available to respond, I need to fix this soon

working on redeploying an older build at the moment to stop the errors and reduce losses, i think i can get back to a stable state, but i don't have the ability to write new code and deploy it.

successfully reployed an older build, so website is back to stable now. communicated the railway outage to my customers. so i think im in a safe state now, which is good! i still can't write new code and deploy it to make progress though :/ would really like to make some progress today if possible! I'm hungry to work!

What happens when you press the deploy button?

will try that again now!

okay it just popped a toast that said "deployment approved!" and it started building. then I see this warning icon increment (screenshot), and it looks like the build failed actually…. okay i might have just been misunderstandin the UI! I think this is probably a build failure on my end!

[ 9/11] RUN npm install && npm run install:server && echo "Checking if service type…" && if ! echo "webapi production" | grep -q "webapi"; then echo "Service is NOT webapi - installing worker dependencies"; npm run install:worker; else echo "Service IS webapi - installing client, analysis-client, audio-rendering, and audio
packages"; npm run install:analysis-client && npm run install:audio-rendering && npm run install:realtime-spectrum && npm run install:audio-player && npm run install:audio-kit && npm run install:social-sample-pack && npm run install:client; fi;
273ms
/bin/sh: 1: npm: not found
Build Failed: build daemon returned an error < failed to solve: process "/bin/sh -c npm install && npm run install:server && echo \"Checking if service type…\" && if ! echo \"$RAILWAYSERVICENAME\" | grep -q \"webapi\"; then echo \"Service is NOT webapi - installing worker dependencies\"; npm run install:worker; else echo \"Service IS webapi - installing client, analysis-client, audio-rendering, and audio packages\"; npm run install:analysis-client && npm run install:audio-rendering && npm run install:realtime-spectrum && npm run install:audio-player && npm run install:audio-kit && npm run install:social-sample-pack && npm run install:client; fi;" did not complete successfully: exit code: 127 >

NPM error aside, if you were to push a new commit, would it also go into pending approval?

yea that is what happened the last time i tried to push a new commit

Right, but I'm asking what happens if you try again.

im not sure what the npm error is yet, since the build successfully builds and deploys on dev, but not on prod. both are using the same Dockerfile and both show the Node install step as cached. so i think the npm error is related to some bad cached layer for the Node install step, not sure if this is bug on my end or on railways end yet, but this is the first time ive seen this error, digging into it more

will try again now

just pushed a small change and ran the dev and prod builds. this time, i did not have to "approve" the request on prod, which is great! still getting the npm build error, but maybe the github approval confusion is resolved?

trying a build with NO_CACHE=1 to see if it fixes

Can I ask you to create a new help thread about the npm error, since the original topic of this thread has been solved?

sure! thank you for your help! I really appreciate it 🙏