679

So today I discovered that there's a cron job that holds non-reproducible state that died, and now our system is fucked.

The cron job doesn't live inside any source control. This morning it entered a terminal state, and because it overwrites its state there's no way to revert it.

I'm currently waiting for the database rollback and have rewritten it in a reproducible/idempotent way.

you are viewing a single comment's thread
view the rest of the comments
[-] wise_pancake@lemmy.ca 22 points 1 week ago

I was able to do that

Turns out there was a second bug which triggered this one, and a bug I found in this script that I thought was responsible was happening silently for months.

Now three bugs are squashed

this post was submitted on 16 Apr 2025
679 points (100.0% liked)

Programmer Humor

22836 readers
539 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS