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.

  • wise_pancake@lemmy.caOP
    link
    fedilink
    arrow-up
    100
    ·
    29 days ago

    He does charge a consulting fee to “fix” these issues

    Almost all of them are dumb shit like this, where something is built in super hacky and dumbass ways.

      • Agent641@lemmy.world
        link
        fedilink
        arrow-up
        18
        ·
        28 days ago

        Judgement day postponed indefinitely due to “Object reference not set to an instance of an object”

        • kiagam@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          28 days ago

          I don’t know why but this is the first time I read this phrase and it actually makes sense.

          I knew exactly what it meant before, but it didn’t make sense until now