a year ago
I pushed a new commit that just changed some way data was handled, and now all my commits are stuck on creating containers. No big changes to my code and no errors, everything still works fine when running on my computer
16 Replies
a year ago
An internal ticket has been attached to this thread. Updates will be relayed in this thread, so keep an eye out!
Status changed to In Progress Railway • about 1 year ago
a year ago
Hello,
We are aware of the issue and have attached a ticket to the help station thread, you can expect to see updates here.
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
But to answer what happened -- It looks like your deployment coincided with a Railway deployment, which delayed the container restart. We are looking to reduce impact from this in the product, but I don't have an ETA.
Since it a fairly large image, you should generally see your builds go out in under 2 minutes, as that has been the general mark you've been hitting. It should be rare that it takes longer like you experienced today.
Best,
Brody
i have bug fixes and a new client update that relies on these new commits
a year ago
you can push them, I'm not seeing any reason why they wouldn't go out at this time
a year ago
Update: An internal ticket linked to this thread has been changed to Todo.
a year ago
Update: An internal ticket linked to this thread has been changed to Completed.
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Hello, update here -
I'm not sure if you saw the incident today, but this morning it went widespread, so we called an incident and dug into the root issue, we believe we have fixed it, and there should be no chance of extended deployment times anymore.
But if you see anything, please let us know!
Status changed to Awaiting User Response Railway • about 1 year ago
a year ago
!s
Status changed to Solved brody • about 1 year ago