a year ago
its a build that i used before, now when i redeploy my app, it takes around 30 minute and it times out, it seems to have some issues installing pip packages. lookslike slow network. stack is a fastapi app.
ⓘ Deployment information is only viewable by project members and Railway employees.
8 Replies
a year ago
Could you please redeploy and see if you're consistently running into the same issue? We haven't had any network changes on our end so wondering if this could be a transient issue upstream
Status changed to Awaiting User Response Railway • about 1 year ago
chandrika
Could you please redeploy and see if you're consistently running into the same issue? We haven't had any network changes on our end so wondering if this could be a transient issue upstream
a year ago
yes, with the new deployments are still having the same issue. also with the other enviroments (staging/prod) both experiencing the same issue.
Status changed to Awaiting Railway Response Railway • about 1 year ago
4bade3
yes, with the new deployments are still having the same issue. also with the other enviroments (staging/prod) both experiencing the same issue.
a year ago
i also tried to change the region to US west (from US East) but it was no help either.
a year ago
Hmm, I understand there's no code changes — have there been any configuration changes made within Railway since that last successful deploy?
The package installation is taking unusually long and the ones that were installed much faster in your older successful deploy are taking several more seconds
Status changed to Awaiting User Response Railway • about 1 year ago
chandrika
Hmm, I understand there's no code changes — have there been any configuration changes made within Railway since that last successful deploy? The package installation is taking unusually long and the ones that were installed much faster in your older successful deploy are taking several more seconds
a year ago
no configuration changes either. it is the same code
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Thanks for sharing that, I’ve raised this and we’re investigating this internally. In the meantime, may I have your permission to redeploy your service? Could you also please share your requirements.txt and I’ll try to recreate this issue on my end and go from there?
Status changed to Awaiting User Response Railway • about 1 year ago
chandrika
Thanks for sharing that, I’ve raised this and we’re investigating this internally. In the meantime, may I have your permission to redeploy your service? Could you also please share your requirements.txt and I’ll try to recreate this issue on my end and go from there?
a year ago
Great, i just redeployed it and it worked. it took 78s to build. thank you very much for your support. for your recreation purposes this is the requirements file attached.
Attachments
Status changed to Awaiting Railway Response Railway • about 1 year ago
a year ago
Woohoo! Thank you for the requirements.txt and super glad to hear it worked 
! Happy building 
!!
Status changed to Awaiting User Response Railway • about 1 year ago
Status changed to Solved chandrika • about 1 year ago