Build won't start
sat in "initializing" for 10 minutes and then failed. there are no build logs
51 Replies
Project ID:
04fd5981-96be-411f-9465-a500c96052d304fd5981-96be-411f-9465-a500c96052d3
Weird issue... Mind creating a new project and kicking off a new build?
linked to the same gh repo?
also appears not to be doing anything
That's very odd. Can you send the repo?
it's private
I can add you if you provide username
Works for me, my username is ItsGoldeneyes
invited
https://github.com/goleary/otter-new/commit/f1e715336bb97a77e095f23d3959dc6fc5f2c549 deployed fine
Is that a specific commit you're pointing me to? The url is 404ing
did you accept the invite?
What's the commit message for it? I can search for myself
yes
weird "tooltip fo transaction name"
is the commite message
Got it
hash f1e715336bb97a77e095f23d3959dc6fc5f2c549
https://github.com/goleary/otter-new/compare/f1e715336bb97a77e095f23d3959dc6fc5f2c549..main to see all changes
fwiw i'd expect the build on the second project to faile due to missing env variables
but it also just hangs forever
Nothing is standing out to me as a major config change from that commit onward. I don't see a reason why the build would get stuck at initializing
i can run the build locally
Unfortunately I'm not a ts dev so I won't be able to help you troubleshoot this, but I'll flag this thread with the team and they will review tomorrow
It's likely an issue on their end, but maybe @Brody has some suggestions
i doubt this is a code issue, if so theyd at least get to a failed build
Agreed
word we'll i'll keep an eye out for tomorrow
lemme know if anyone else wants to take a peek in the repo
Thread has been flagged to Railway team by @Adam.
thanks!
No prob, best of luck
and youve tried creating a whole new project and service?
yup
same repo
same thing happened
just for fun, deploy a different repo to the same service
the second service i created?
whatever one gets stuck
they both do
then its your pick
nada
tried a template (cal) and nothing still
could be related to this one -https://discord.com/channels/713503345364697088/1199889737104765008/1199889737104765008
it could be but they haven't given any information about anything
true
cal deployed
but with no build logs
maybe the logs are slow to come in
though this definitely is looking like a platform issue
@fp - builds stuck at initializing for long periods of time, when/if they go through they are missing their logs
im getting this same error
stuck at initialization?
@Brody yup, and after 10-11 mins, it eventually fails with the following message: "Cannot create code snapshot right now, please review your last commit or try again
If this error persists, please reach out to Railway team"
Just created a separaet post for this as well https://discord.com/channels/713503345364697088/1199945195479904276
the team has their eyes on this issue, please check https://discord.com/channels/713503345364697088/846875565357006878 for updates
If you have a build initializing for a while you can cancel it and try to redeploy.
@real.spidey @goleary for visibility
I've seen some projects with an initializing build but newer builds succeeded.
got it, thanks for the ping @Brody@Mig , will retry
let me know if it builds correctly after 👍
Please go ahead and try again @goleary
build logs are flowing now, thanks!