&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+acetone
+dr|z3d
+hagen
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
Arch
BubbRubb
C341
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest64675
Irc2PGuest68228
Irc2PGuest82088
Onn4l7h
Onn4|7h
Sleepy
SlippyJoe
T3s|4_
Teeed
aargh
ardu
b3t4f4c3___
cumlord
death
dr4wd3
duanin2
f00b4r_
llamafan717
nnm--
not_bob_afk
ohThuku1
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
wew-
x74a6
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