52, 53, and Other Numbers That Ruin Your Evening
With the scheduler starvation bug fixed, the next client finally ran — and immediately failed for a much dumber reason. Shared logic assumed channel 52. It was actually assigned channel 53.
With yesterday's starvation bug actually fixed, Client B finally got to run for the first time in a while. Good news. It then immediately failed, which — after the RNG-bug-that-wasn't — I was almost prepared to find funny.
The dumbest possible reason
Shared logic across the SecureRandom clients assumed a hardcoded startup channel: 52. Client B's actual assigned channel, in this particular configuration, was 53. One number. Off by exactly one, in a config-dependent way that the previous starvation bug had been successfully hiding, because Client B hadn't gotten far enough to hit this problem until the scheduler was actually letting it run.
Why I'm including something this small in the same journal as microkernel decisions
Because this is real, and pretending a project this size is only made of grand architectural decisions would be dishonest about what actually eats an evening. Extremely complicated systems — capability-based security, custom entropy subsystems, a whole staged GPU driver plan — can still faceplant on a boring hardcoded number that nobody double-checked against the actual runtime configuration. That's not a contradiction. That's just what real systems work is like most of the time, in between the entries that make for good story arcs.
The fix, and keeping it that size
The correction was narrow and configuration-aware: stop assuming 52, read the actual assigned channel for the configuration in question. I'm not going to dress this entry up as more architecturally significant than it was. It's a one-line-shaped bug with a two-day setup because a bigger bug was standing in front of it the whole time.
Two real bugs, back to back, both hiding behind symptoms that pointed somewhere else entirely. That's most of what debugging actually is on a project like this — and now that both were behind me, it felt like a reasonable point to step back and take an honest look at where the whole project actually stands, which is exactly where this retrospective run closes out.
Originally published on The Weekend Report: https://theweekendersproject.com/report/52-53-and-other-numbers-that-ruin-your-evening