Conversation

Notices

1. Embed this notice
   :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Wednesday, 21-Aug-2024 02:43:21 JST :apa: スプリットショックウイルス †

   • かき@GNUsocialJP

   I assisted in 2.7.1 development ✋ 😮 ✋

   https://git.pleroma.social/pleroma/pleroma/-/issues/3304

   • Sick Sun likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Wednesday, 21-Aug-2024 02:43:20 JST 

     in reply to
     @splitshockvirus I've intentionally let the oomfie's instance rot in order to trigger the job queue constipation bug so that the dev I gave ssh keys to could debug it. All without his consent.
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Wednesday, 21-Aug-2024 03:20:00 JST feld

     in reply to

     • 
     @mint @splitshockvirus btw on any of your servers that did the Oban downgrade in feld/debugging branch will need to run the latest feld/debugging branch from when I re-upgraded it or else when you go back to stable releases it will still have the Oban v12 schema reverted. It can be fixed manually but running latest feld/debugging (a4293a8e) will fix it
     
     and on that note I'm going to push my telemetry/logging changes into that branch which will help people monitor the health better just by looking at the logs
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Wednesday, 21-Aug-2024 03:21:44 JST 

     in reply to

     • feld
     @feld @splitshockvirus I haven't pulled the Oban downgrade since I didn't want to lose its dashboard, it's been very useful in monitoring the state of the instance, already paying off during DDoS for example.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 23-Aug-2024 06:48:22 JST 

     in reply to

     • feld
     @feld @splitshockvirus Looks like what I assume the fix for the issue just landed in Oban repo not too long ago.
     https://github.com/sorentwo/oban/commit/e59973f81dfd822aad94cadca94380388e2024f1