a month ago
We are investigating source provenance for deployment 414592c3-1cb9-4148-b916-118ae9e990fd.
Railway reports that this deployment used GitHub commit:
ea7419f9a72bc143f635fa4b3e85ef0d0a75a1f5
However, the Railway lint/build context referenced:
src/components/manager-system/ManagerCommandCenterDetail.tsx
That file does not exist in the GitHub tree for the reported commit, and it also does not exist in the immediately preceding successful deployment commit.
Please provide either:
the exact source snapshot or file manifest Railway used for deployment 414592c3-1cb9-4148-b916-118ae9e990fd, or
a provider-side trace/explanation showing how src/components/manager-system/ManagerCommandCenterDetail.tsx entered the build context.
Repository: travis-dunn28/producer-command
Branch: atlas/direct-interaction-vs01-r2
This is specifically a Railway deployment source-provenance investigation, not a request for application debugging.
1 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Try to set NO_CACHE=1 in your service variables to rule out any caching issues, and see if that file still shows up in the build context.