#DuckDuckGo going down again (#HugOps to everyone there) has really reminded my how much my unconscious workflow depends on a search engine these days.
Hi folks, you may have noticed that we had an outage for a couple of hours this morning on our app, website and instance. We are back online now and hopefully things should be back to normal, but please bear with us if there are any issues for the next while.
Stressful work day ahead. Things I wrote are being remote installed in user premises, and we had to make last-minute changes I'm not entirely convinced about. Fingers crossed.
Rails app won't start because of uninitialized constant XYZ from somewhere in zeitwerk (which appears to be wasting much Zeit und causing much Werk right now). The weird thing is, the string for which XYZ is a placeholder appears nowhere in the codebase, in any gems, in any code on GitHub, or anywhere on the internet!
I do appreciate it when things break and people start complaining about "when will work again" and "how outdated and unusable the broken thing is" and "how other solutions would be much better" instead of asking how to help fixing things.
At this point here is a #hugops to all Fedi admins dealing with spam. By pure luck (due to the hard work of my instance admins) and serendipity (my mostly-limited-to-followers reading habits) I only received a single spam message so far. Rock on!
There's a story of developer (me) having a no good very bad morning because of this loaded gun that Rails leaves on the table.
Just imagine you're fixing some production data and you accidentally type User.update instead of user.update and realise you just updated not one, but every single record in the database with the same value.
Also, thank goodness for PostgreSQL point-in-time database restoration 😓
(I updated a field excluded from audit logs, of course)