This video is a scathing critique of the perceived mismanagement and poor quality of code within GitHub Actions runners, specifically targeting a long-standing bug causing "zombie processes" that waste compute resources and cost customers significant money. The speaker reserves the usual courtesy of not mocking random code because this poor quality originates from one of the world's largest corporations (Microsoft/GitHub). The main focus is a specific scheduling/timing bug that, in one documented case, caused a single runner process to execute for over 5,000 hours, costing an estimated $2,400 in compute time alone. The historical context reveals a series of increasingly "deranged" attempts to implement a "safe sleep" function in Bash, starting from convoluted Stack Overflow hacks involving ping and echoing to /dev/null, eventually settling on a flawed loop condition (while date > X) that fails to account for execution time drift, leading to infinite loops. The speaker also briefly mocks a recent, poorly implemented refactoring in another part of the Actions codebase that allegedly introduced new bugs. The tone is highly critical, suggesting corporate indifference to fundamental product stability. As an aside, the creator begs viewers to subscribe to reach 1 million subscribers.
Critique of GitHub Actions Runner Code and Management
0:00:01 Uncharacteristic Criticism: Speaker breaks his rule against mocking general code because the poor quality stems from a major corporation (Microsoft/GitHub) that has ignored pleas to fix critical bugs costing companies real money.
0:00:52 Subscriber Push: The creator is under 23,000 subscribers from 1 million and demands viewers subscribe. I don't care about the sponsorship plug, but perhaps reaching a milestone is a rational goal if audience size correlates with platform viability.
0:01:07 GitHub Actions Runners are Flawed: The core issue is the state of GitHub Actions runners, which allegedly have been "limping" for a decade with inexcusable bugs.
0:01:19 Extreme Consequence: The company Zigg left GitHub for Codeberg entirely due to these Actions bugs, citing "inexcusable bugs" and neglect.
0:01:36 Vibe Scheduling: GitHub Actions allegedly started "vibe scheduling," running jobs randomly without the ability for users to intervene, causing CI backups.
0:01:57 The "Deranged" Code: The central problem is a set of four lines in the runner code responsible for timing/sleeping, described by another programmer as "utterly deranged."
0:02:48 Historical Deep Dive: The original runner code implemented a "sleep" function using hacks derived from 16-year-old Stack Overflow answers, trying to use ping (which sends packets every 1 second) as a timer when the sleep command wasn't available.
0:04:05 The "Safe Sleep" Escalation: Early implementations involved highly inefficient methods like echoing "sleep" 5,000 times to /dev/null, which was noted as CPU intensive.
0:04:38 The Final Flawed Form: The long-standing version used a structure akin to while $SECONDS -lt $TARGET, which is fatally flawed because system load can cause delays between loop iterations, causing the loop to overshoot the target and run indefinitely (a "zombie process").
0:07:21 The $2,400 Bug: One specific instance saw a single runner process run forever for 5,135 hours, costing approximately $2,400 based on the cheapest CPU minute rate.
0:07:56 Delayed Fix: The crucial fix—changing the condition to less-than-or-equal-to (<=) instead of greater-than (>)—was submitted but ignored for over a year before being merged, suggesting profound organizational inertia or incompetence.
0:08:15 Additional Horrors: Speaker briefly points to another recent diff where a refactoring intended to clean up code allegedly made it more complex and introduced new bugs ("Failed to hash files").
0:09:38 AI vs. Human Failure: The creator humorously notes that looking at such profoundly bad human-written code restores his faith in AI coding, as an AI likely couldn't be this creatively awful.
0:09:54 Corporate Indifference: The speaker concludes that Microsoft/GitHub simply does not care about the stability of this multi-billion dollar product that millions rely on.
10:32 Sponsorship Plug: Plug for boot.dev coding courses.