2 years ago
I've a bunch of old PR environments that are unused and using a lot of RAM, is there a way to do the above?
45 Replies
2 years ago
357a7a66-a372-47f0-b2ae-2d8e2b6f1f32
2 years ago
I don't use pr envs but I could have sworn they are supposed to be removed after the pr gets merged
2 years ago
maybe it's a setting somewhere? could you have a look around? if not, I'll escalate
2 years ago
lol didnt see this, I was going to open another thread
2 years ago
well I looked around, couldnt find anything, but again we've a lot of PR enviroments that are just sitting there

2 years ago
have those pr environments been merged?
2 years ago
yep

2 years ago
shoot wait
2 years ago

2 years ago
yep
2 years ago
I see
2 years ago
is every single pr environment sticking around? or do some of them get cleaned up after merge?
2 years ago
some of them get deleted 🤔

2 years ago
is that comment correct? did the environment on railway get deleted too?
2 years ago
yep, thats #107 and it got deleted
2 years ago
I tried to search for any pattern between the pull requests but couldnt find any
2 years ago
okay so it's just flakey then?
2 years ago
hmmm found two that said "deleted"

2 years ago
but are still in Railway's dashboard
2 years ago
okay so it's very flakey then?
2 years ago
yep seems so
2 years ago
will escalate
2 years ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response brody • over 1 year ago
2 years ago
*will remove the active deployments but preserve the environment as they're costing us money
2 years ago
Thanks for raising this issue, we'll take a look. Have added the issue to triage to investigate. Thanks.
2 years ago
This thread has been marked as solved automatically due to a lack of recent activity. Please open a new thread if you require further assistance. Thank you!
Status changed to Solved Railway • over 1 year ago
2 years ago
yo @Brody
2 years ago
and you are still seeing this right?
2 years ago
the last one I saw was 8 days ago

2 years ago
and that pr has long since been closed?
2 years ago
yep, that PR was merged about instantly
2 years ago
gotcha, for context the ticket that was created from your bridged help thread was fixed and marked done 3 weeks ago.
but this has popped up again (another user reported it) and a new ticket was made, i will add this discord thread to the new ticket so i can circle back when the new ticket is marked done
a year ago
any update on this? still having issues

a year ago
does it exist?
a year ago
no, the branch doesnt even exists anymore
a year ago
how long ago was that pr opened
a year ago
2 months ago
a year ago
oh well then it's not going anywhere, you'll have to delete it haha
a year ago
oh so there has been a fix since then?
a year ago
partially
a year ago
I'd say an improvement
a year ago
we found that PR's that opened and closed in rapid succession were getting missed and left hanging as pr environments
a year ago
great, will delete it
a year ago
update here, we just merged another pr that should fix even more edge cases, so please let us know if you see this again
a year ago
(still isn't going to delete old envs though)
I'm still seeing this on PR's merged ~3 weeks ago
project-id: 7780fb34-fbdd-4a72-bfcc-95b83970ef8d
9 months ago
please open your own thread