a month ago
Service name: dars-platform
Builder ID: builder-qpvwnj
Failed deployment IDs:
dcc786d5-dd63-4ff1-9521-d56068d898a4
cb373e06-6773-4272-9df7-62732587282d
7cc1851f-423e-4b4d-97b4-570985028a35
Repository: hamza-abu-abduRrahman/dars-platform (main branch)
Issue: Intermittent checksum calculation failures in the build daemon for files copied directly from the build context (go.sum, configs.example.yaml)3 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 26 days ago
a month ago
Try selecting the service, press Ctrl/Cmd + K, and deploy latest commit or source image.
0x5b62656e5d
Try selecting the service, press Ctrl/Cmd + K, and deploy latest commit or source image.
a month ago
I just pushed new changes and attempted to deploy again.
The build failed with the exact same error:
"failed to compute cache key: failed to calculate checksum of ref: /go.sum: not found"
This confirms this is not a code issue — it's a Railway build infrastructure bug.
The files (go.sum, configs.example.yaml) exist in the repository,
but the build daemon intermittently fails to calculate their checksums.
My production service is currently offline and blocked by this bug.
I need immediate help:
- A fix from Railway's infrastructure/builder engineering team, OR
- A technical workaround
Please escalate this urgently.
Attachments
a month ago
Resolved ✅
Root Cause: The build was failing because the rootDirectory was not configured correctly. The Go project files (go.mod, go.sum, Dockerfile) were located in a subdirectory, not at the repository root. The builder was looking for them in the wrong place.
Fix: Set the correct rootDirectory in the Railway service configuration to point to the subdirectory containing the Go project. This tells the builder to use that directory as the build context.
Status: Deployment now builds and deploys successfully.
Status changed to Solved 0x5b62656e5d • 25 days ago