18 days ago
It's failed both front-end and back-end. This is diagnost log i got. So what could I do to fix this?
Infrastructure Error
Run automatically
Both wapchill-backend and wapchill-frontend are failing to build because the bun runtime is not available during the build step. The Railpack build cache appears to be skipping the mise package installation step that
provides bun and node, causing every build since May 19 to fail with "bun: not found". No code or config changes were made between the last successful build and these failures. Contact Railway support to investigate and
clear the build cache.
3 Replies
Status changed to Awaiting Railway Response Railway • 18 days ago
17 days ago
Any response to this
17 days ago
This build failed due to a recurring infrastructure issue with the Railpack build cache. The cache is intermittently skipping the mise package installation step, so the bun runtime is never installed and the build command fails with "bun: not found" (exit code 127). A successful build ran just 11 minutes earlier with identical configuration, confirming this is not a code or config problem.
17 days ago
scheduling build on Metal builder "builder-uwqosa"
scheduling build on Metal builder "builder-uwqosa"
fetched snapshot sha256:9e92c1ccadc45a54b263ab7c89c1f1aa334ebaa2d78856bf18311f225150f45f (6.2 MB bytes)
fetching snapshot5.9 MB349ms
unpacking archive25 MB218ms
using build driver railpack-v0.23.0
╭─────────────────╮
│ Railpack 0.23.0 │
╰─────────────────╯
⚠ Script start.sh not found
Steps
──────────
▸ build
$ bun run --filter '@wapchill/backend' buildDeploy
──────────
$ bun run --filter '@wapchill/backend' startload build definition from ./railpack-plan.json
1ms
copy . cached
1ms
bun run --filter '@wapchill/backend' build
940ms
sh: 1: bun: not found
Build Failed: build daemon returned an error < failed to solve: process "sh -c bun run --filter @wapchill/backend build" did not complete successfully: exit code: 127 >
Status changed to Solved Anonymous • 17 days ago