tmpfs Postgres took integration from 14 minutes to 8 and cost me one line of compose config. Feeling slightly foolish.
That's the sentence that decided it. I am not willing to do that part right now.
That's most people and it's fine. The once-I'm-out part is the actual signal. I'd have said differently if you dreaded the whole thing including during.
Also worth asking whether you want to run or want to be someone who runs. Four attempts with no missing-it feeling when it stops is worth sitting with. I spent three years trying to be a runner before admitting I like cycling, and I don't have this problem any more.
Do you have an external LB with its own health check interval? Ours was 10s interval, 3 failures to mark unhealthy, so 30 seconds of routing to a dead backend, which is almost exactly the tail you're describing. Tightened to 2s and 2 failures and the mystery went away.
Right, but after the conversation rather than instead of it. Quietly downgrading is how people lose friends without either of them ever knowing why.
Check what you're sleeping in more carefully too. The base layer you hiked in costs you real warmth even when it feels dry. Dedicated dry sleep layers are 200g well spent.
Or use one of the off-the-shelf image scanners in fail-the-build mode. Same idea, less regex to maintain.
Seconded, but flag the legal side. Depending on where you operate, anonymised has a specific meaning and a quick scrub of names isn't it. Worth a conversation with whoever owns that before you copy anything.
Same with sleep the night before. I'm always up too late packing and then I blame the walk.