FYI: I’ve re-opened up search for anonymous use. So things like this now work without having to have an account on this pod or login. 👌 #search #twtxt

Fixed.

Confirmed. Fix inbound.

Is it just me or is there a display bug for “Yarn”(s) that are duplicating the root twt? 🤔

This is an example of what I believe every SRE should master and whatever Post Incident Review (PIR) should focus on. Where did the system fail. What are the missing or incomplete Safety Controls.

Then I cleaned up my shell history of all of the invocations I ever made of dkv rm ... to make sure I never ever have this so easily accessible in my shell history (^R):

$ awk '
  /^#/ { ts = $0; next }
  /^dkv rm/ { next }
  { if (ts) print ts; ts=""; print }
' ~/.bash_history > ~/.bash_history.tmp && mv ~/.bash_history.tmp ~/.bash_history && history -r

So I re-write this shell alias that I used all the time alias dkv="docker rm" to be a much safer shell function:

dkv() {
  if [[ "$1" == "rm" && -n "$2" ]]; then
    read -r -p "Are you sure you want to delete volume '$2'? [Y/n] " confirm
    confirm=${confirm:-Y}
    if [[ "$confirm" =~ ^[Yy]$ ]]; then
      # Disable history
      set +o history

      # Delete the volume
      docker volume rm "$2"

      # Re-enable history
      set -o history
    else
      echo "Aborted."
    fi
  else
    docker volume "$@"
  fi
}

This weekend (as some of you may now) I accidently nuke this Pod’s entire data volume 🤦‍♂️ What a disastrous incident 🤣 I decided instead of trying to restore from a 4-month old backup (we’ll get into why I hadn’t been taking backups consistently later), that we’d start a fresh! 😅 Spring clean! 🧼 – Anyway… One of the things I realised was I was missing a very critical Safety Controls in my own ways of working… I’ve now rectified this…

@bender@twtxt.net Please remind me to fix this after I’m done with this cachet branch and it’s merged 🤞

Okay that’s a bug 😆

Does mentioning @prologic@twtxt.netdoesnm.p.psf.lt not work? 🧐

@bender@twtxt.net I know! 😂 Thankfully I think I fixed most problematic bugs 🤞

@movq@www.uninformativ.de Just keep them for a while.

@bender@twtxt.net Whoohoo! 🥳

@lyse@lyse.isobeef.org Very nice 😊

@lyse@lyse.isobeef.org Haha yeah 🤣 And thanks I’ll take a look but honestly it’ll be fine 😆

@movq@www.uninformativ.de Nah it’s okay 🤣 It would only be a partial restore anyway 😭

I need to get Peering working again on this branch! That will drag in many Twts Twts I now no longer have 😭

At least I’ve fixed many bugs with the new SQLiteCache 🤣

@aelaraji@aelaraji.com Sounds cool! 😎

@movq@www.uninformativ.de We’ll recover just fine right ? 😆 It’s only 4 months worth of posts 😅 Not like it’s the end of the world 😂

Oh well, let’s just start over! 🤣

Oh well. I’ve gone and done it again! This time I’ve lost 4 months of data because for some reason I’ve been busy and haven’t been taking backups of all the things I should be?! 🤔 Farrrrk 🤬