sina
Missing GitHub Pushes After Branch Autoswitches Back To Main
Not sure if this is a bug or intended, but I'm seeing the following unexpected behavior:
1.
service1 set up to deploy on push to main, things work fine
2. update service1's branch to branch1; push to branch1 deploy works fine
3. merge in branch1 to main via github; railway seems to automatically reset my branch for service1 to main
4. despite the settings showing the branch as main, subsequent pushes to main don't trigger deployments. I seem to have to manually unlink and relink the github branch for it to work again
I'm not sure what exactly the best alternative is here, but it's quite confusing for the UI to show the branch connection reset to main while pushes to main don't trigger redeploys.
I was noticing this in my "prod" services, and went ahead and made a minimal repro (in the projectID linked below)6 replies
Service Returns Sporadic 503s, due to DDOS protection?
My api service periodically returns the railway error html page with a 503 code. I believe this issue is on the railway side, as I don't see it crop up locally in similar testing scenarios.
In my case I'm testing the frequency I can call my API; are there inherent rate limits the railway platform enforces? I poked around in the doc and couldn't find anything related to this. I'm testing with ~hundreds of requests per sec
113 replies