0xFFFE

It appears the problem existed before the lila3 was deployed on 11/22. If you notice the GC graph. The number of GC cycles/minute kept increasing gradually starting on 11/10 and almost doubling on 11/21. The 11/22 deployment of lila3 reset the graph and since you have been restarting everyday since, we can't see the growth of more than a day. My wild hunch is a code push on 11/10 causing a memory leak, worth checking in my opinion.

Not too different from San Fran then!

If you don't have anything good to contribute at least don't be a dick to others. Life can turn on a dime and any of us could be in a similar situation.

You may be able to control the place of "landing" but you can't claim to control the airspace above it.

Totally off topic. I am not an UI/UX designer but why can't the page scale to the size of the screen? Sure I could ctrl/cmd++ but is it hard to detect the screen size? Genuine question, not trying to be condescending.

Trappist 1

My manager during the recent 1:1 said I have been a valuable employee. Should I be worried?

You would have added some expletives too if you had worked as a support engineer.

You need to keep it fueled for it to maintain whatever orbit it gets pushed into. Orbital decay and everything.

C is generally better because it doesn't treat you with kid gloves, if you don't know what you are doing you will get fucked in the ass. That said, any competent engineer would know what tool to use to solve a given problem. You don't use a sledge hammer to fix a watch.

Tap analogy can be subjective depending on where you are located on the planet :)

Yes, I agree that readability could have been better.

Imagine if these incidents happened in an on-prem infra with such regularity. Heads would have rolled.