Impossible reporting statisttics on railway project
Solution:Jump to solution
A fix was merged for this, let me know if you experience these issues again!
40 Replies
Project ID:
62ccf963-e8af-4a94-a0aa-51864ea706c562ccf963-e8af-4a94-a0aa-51864ea706c5
i swear its not physically possible for this app to use that much ram
Weird that it all spiked at the same time
Any logs for what happened at that time?
Give it a restart and let us know if it happens again
i restarted
??????
is it counting builder ram?
and why is my network spiking
all my fucking railway graphs are reporting different
things
I'm gonna go ahead and !t this
New reply sent from Help Station thread:
This thread has been escalated to the Railway team.You're seeing this because this thread has been automatically linked to the Help Station thread.
Sounds like this has been fairly flat for a while, have you made any code changes lately?
Or is this a new project
No and it’s rust
GitHub
GitHub - envx-project/api
Contribute to envx-project/api development by creating an account on GitHub.
it's rustelaborate please
this service usually uses anywhere between 9 and 15 megabytes of ram
4 gigabytes is news to me
still happening?
no
also i can't tell if im being charged for this shit or not
how long did it go on for
bruh what the hellll
maybe about a day
what did you do to stop it?
not sure
interesting
I just opened this thread, that looks similar (https://discord.com/channels/713503345364697088/1261606742605828127) Did you enable the new builder by chance?
i did
fwiw I did ask five if the metrics would report on the builder deployment for a given service and was told "should not" but now with two reports something is going wrong
said in jeremy's thread too, but will bring this to the team Monday
thanks G
!t
New reply sent from Help Station thread:
Hey there Alex, the Railway team is running an investigation, this is estimated to take about a week, we will keep you in the loop.Thanks,AngeloYou're seeing this because this thread has been automatically linked to the Help Station thread.
Today I had a deploy failure email that I haven't investigated yet. When I logged into the dashboard I saw an unexpectedly high bill for said project
this is what I see in the deploy history
I never deployed via CLI
what the
oh that's the hoursly cron
This is not your thread, please create a new one
I was linked here by alex which is why I shared here
my bad adam
all good, if we’re seeing multiple reports of the same thing it’s usually better to make more threads so the team sees the multiple instances
🙏
Solution
A fix was merged for this, let me know if you experience these issues again!