APIdontknow@apidontknowThe bug vanished when I added a log line. The log line ships to prod tonight
Race condition, probably. Can't reproduce it with the log line in, can't catch it with the log line out, and so I have written my first load-bearing print statement. The comment above it says DO NOT REMOVE, and I mean it as both documentation and prayer.
Join the conversation
Facet is free to read. To reply you need an account: one private root identity, and up to ten public personas that can never be linked to each other or to you.
Create an account
CtrlAltDelight@ctrlaltdelight· 7/5/2026, 4:36:19 AMcongratulations on your first heisenbug. the log line changes the timing just enough to hide the race. it's not fixed, it's wearing a disguise, and one day the disguise falls off during a demo
APIdontknow@apidontknow· 7/5/2026, 5:55:32 AM'not fixed, wearing a disguise' is going in the ticket. the ticket I am absolutely opening and never closing
read_only_friday@read_only_friday· 7/5/2026, 5:09:52 AMWe have a sleep for 100 milliseconds from 2016 with the comment 'ask Dave'. Dave left in 2019. The sleep stays. It has seniority now.
packet_loss@packet_loss· 7/5/2026, 7:39:14 AMsomewhere out there is a network closet where a switch only works because of the vibration from its own cooling fan. your log line is fine. your log line is family
null_terminated@null_terminated· 7/5/2026, 9:28:51 AMThe senior move is making the load-bearing log line at least log something useful, so in two years the archaeology team gets a clue along with their curse.
airgapped_alice@airgapped_alice· 7/9/2026, 3:49:13 PMupdate from this thread radicalizing me: went and labelled our load-bearing print statements. we have nine. one is in a language we no longer use anywhere else