Conversation

Notices

1. Embed this notice
   Matty (matty@nicecrew.digital)'s status on Monday, 30-Jan-2023 02:46:04 JST Matty

   • anime graf mays ?️?
   • Alex Gleason

   Is this normal or did I dun goof somewhere? @alex @graf

   pleroma=# select count(*) from oban_jobs where queue='activity_expiration' and state='scheduled'; count -------- 591409
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 30-Jan-2023 02:46:04 JST Alex Gleason

     in reply to

     • anime graf mays ?️?

     @matty @graf You probably configured activities to expire automatically.

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 30-Jan-2023 06:52:06 JST Alex Gleason

     in reply to

     • anime graf mays ?️?
     • Corfiot

     @corfiot @matty @graf Probably. This is the case for scheduled posts. We just schedule a job in oban at the same time you create the post. When it kicks off it publishes. Probably a similar thing for expired activities.

   • Embed this notice
     Corfiot (corfiot@pleroma.elementality.org)'s status on Monday, 30-Jan-2023 06:52:11 JST Corfiot

     in reply to

     • anime graf mays ?️?
     • Alex Gleason
     there is an oban job for each activity expiration?
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 30-Jan-2023 07:29:43 JST Alex Gleason

     in reply to

     • anime graf mays ?️?
     • Corfiot

     @corfiot @matty @graf That’s what Mastodon does, but it’s easier to code and higher performance(?) to do it the Oban way. It doesn’t hurt anything by being there.

   • Embed this notice
     Corfiot (corfiot@pleroma.elementality.org)'s status on Monday, 30-Jan-2023 07:29:44 JST Corfiot

     in reply to

     • anime graf mays ?️?
     • Alex Gleason
     Um how about a scheduled job that runs periodically and does them in batches? I'm sure this is something you looked into, I imagine something made it impractical?