Networking
Cloudflare Error 526 and the Redirect Loop: Two Failures, One Setting
Flexible gives you an infinite redirect. Full strict gives you a 526. The documentation says Full or higher, and higher is the one that breaks.
Production debugging, observability, CI failures and the infrastructure layer every service depends on and nobody instruments.
Networking
Flexible gives you an infinite redirect. Full strict gives you a 526. The documentation says Full or higher, and higher is the one that breaks.
Node.js
The quick fix is raising ulimit. The real question is what is holding thousands of descriptors open and never closing them.
MicroVMs
A patched kernel that kept reporting the old version after every reboot. The reboot was working perfectly. My assumption about where the kernel comes from was wrong.
Bug Hunt
Every replica restarted at once during a brief database blip. The health check was working exactly as designed, and the design was wrong.
Docker
Your image builds on a Mac and dies in production. What the error means, how to check an image's architecture, and how to build multi arch properly.
Engineering Culture
A document nobody reads, listing action items nobody does, produced to satisfy a process. Here is the version that actually changes something.
DevOps
The instinct is to start investigating. The first ten minutes are better spent on four other things, and doing them makes the investigation faster.
Bug Hunt
p99 jumped on one service. The database was fine, every dependency reported healthy, and the flame graph pointed at nothing. That turned out to be the clue.
Networking
At-least-once delivery means duplicates are normal operation, not an edge case. Here is how to build a handler that survives them.
Deep Dive
Traditional VMs take thirty seconds. Firecracker takes 125 milliseconds. The difference is everything it refuses to do.
DevOps
A build system with production credentials and the ability to run arbitrary code from a pull request is the most under-secured part of most stacks.
Kubernetes
Exit code 137, a memory graph that looks perfectly healthy, and no application error. Here is why your monitoring missed it and how to find the real number.