@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Chrono
Daddy
Dann
DeltaOreo
Irc2PGuest22388
Irc2PGuest25042
Irc2PGuest43747
Irc2PGuest68968
Irc2PGuest70600
Irc2PGuest74352
Onn4l7h
Over1
Sisyphus
Sleepy_
T3s|4_
Teeed
aargh1
ac9f
b3t4f4c3__
bak83_
combed_tree328
coolbuddy799
cumlord
dr4wd3_
duanin2
leopold
makoto
not_bob_afk
poriori
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
tr
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr
eyedeekay
OK that might be enough to fix gitea for us... if it is I'll write us a postmortem, if it isn't I'll hold off on the postmortem until I actually fix it
eyedeekay
will be back in a few minutes after the backups run
eyedeekay
Well it's not actually fixed but it looks a lot more fixed, downtime should be a lot less noticable
dr|z3d
translation: "I didn't fix it as such, I just threatened it."
eyedeekay
unironically yes
dr|z3d
:)
eyedeekay
Whackamoling deadlocked git subprocesses keeps gitea from crashing too much and speeds up rebooting, that + a caching proxy