43 Replies
Project ID:
56d30439-0f03-4507-96fc-515aa6becfd156d30439-0f03-4507-96fc-515aa6becfd1
Generally, all my builds have suddenly started to hang after some weird flakes
similar to https://discord.com/channels/713503345364697088/1164667174460338268/1164667174460338268 – it seems like 8-12 minute delay on builds starting
I'm also getting a "failed to upload code" error using railway up
4f17b2f6-a89e-43f2-b521-8b9d75da8e69
@thomas builder issues?
Checking
Probably not, checking out this project
theres also this thread reporting the same https://discord.com/channels/713503345364697088/1164667174460338268
Interesting, trying a build myself
might only be an issue with a single builder out of the entire builder fleet
seems healed on my last 3/3 builds
Also having the issue on my end, 2/2 deployments
also having this
same error from github actions as the title of this post
more detail in the build log of my container
ok, elevating
Same issue here
Please continue dumbing information here and reporting what is happening to you
Cannot create code snapshot right now, please review your last commit or try again
If this error persists, please reach out to Railway team
revert code to an earlier commit and still the same issue
Thank you, the more details the faster the team can respond. Are all of you using the
railway up command for this?yes
i am
yes
I've seen 10+ consecutive failures with railway up. Sounds like someone noted the same with github actions potentially?
Thank you, will update as we figure this out
Hanging builds from github merge triggers for me in addition to
railway upFor me, the initial error was on GH actions saying
Multiple services found. Please specify a service to deploy to. which I found weird because it never did it before then I got what OP posted after I specified the service with the ID in the action: railway up --service ${{ secrets.RAILWAY_SERVICE }}Incident created and confirmed: Woops posted the internal link: https://railway.instatus.com/ to follow
Railway - Status
Railway Status
did you recently add a new service (like a db or additional service?) – this new flow appears after you create the second service in your project.
yeah i can see that happening, a new version of the cli was released, the new version no longer guesses what service you want to up to, this was a much needed fix
the cli fix was put in place for a bunch of reasons, one of them being to stop automatic up'ing into a database service
Possible fix in place, please respond if still not working for you
should i redeploy now?
Yes
works
Thank you, and thank you for everyone for piling on this so I could elevate it to the right people. This is how we keep railway running smoothly
first deploy successful for me as well
Thanks for jumping on it, you guys are awesome!
works, brilliant. thank you 🙂
No i did not and I only have 1 service
But it seems to work now thanks
my bad – apparently there was a cli change for this
the cli change would not have caused your error
yep the cli wont up to anything automatically anymore
We hit the following error on Github workflow during deployment - Could this be related to CLI change:
yes it is
Cool, will bump up our CLI version and try again
it should be using latest, thats why you got this error, just specify the desired service with the service arg
will be improving that error though
(milo will)
That'd be awesome, thank you 🙏
its trying to ask you for a service to link, but prompts arent an option on non-tty terms, so instead it should tell you that you need to use the service arg on the up command
silly bug, will very likely be fixed on the next minor version
https://github.com/railwayapp/cli/pull/460 pr that adds more context
GitHub
Add context if terminal is TTY by Milo123459 · Pull Request #460 · ...
This fixes a silly bug where the terminal thinks it is TTY. Unfortunately, we can't do anything about that but we can add extra context to the error.
(pending additional testing)