I'm Urav. I build things with code.
Every day a bot grabs a commit (one of mine, someone I follow, or a stranger's), an AI names and roasts it, and it ends up as a strange attractor.
Chaos ███░░░░░░░ 35 · Mood
murtazahr/Kafila by @murtazahr · 96b374b
agent: skip the batch tests when MLX is absent
Two tests build a batch, which allocates an array, and had no guard. Without the
runtime those calls resolve to null and the process dies with rip=0x0 rather
than failing a test -- so the package takes
…
Ah, the classic CI surprise: an invisible dependency silently crashing the test suite. This fix wisely adds a skip for absent runtimes, turning potential 'rip=0x0' disasters into civilized, guarded test executions. It's pragmatic code, even if co-authored by a large language model whose understanding of hardware is questionable at best.
captured 2026-08-24
What is this?
flowchart LR
commit["🌌 daily commit"] -->|diff| gemini["Gemini"]
gemini -->|chaos + mood| attractor["Lorenz attractor"]
gemini -->|title + roast| exhibit["today's exhibit"]
attractor --> exhibit
A GitHub Action runs daily and picks a commit: mine if I've pushed recently, otherwise something from my network or a starred repo, and the Linux genesis commit as a last resort. Gemini gives it a name, a roast, a chaos score (0-100), and a mood color. Those become a Lorenz attractor: chaos controls how wild the butterfly gets, mood tints the gradient, and the commit hash sets the starting point. The math is identical every run, so the commit is the only thing that changes the picture.