Conversation

Notices

1.  (mint@ryona.agency)'s status on Tuesday, 15-Oct-2024 01:51:36 JST 

   • :blank:
   • ♡ miss olivia ♡
   • feld
   @feld @i @olivia There was, I wasn't affected, some used AntiMentionSpam, keyword or reject policies. That said, it isn't related to current issue with RemoteFetcherWorkers piling up into millions (which I believe are only spawned by pinned post fetching pipeline in vanilla pleromer).
   • † top dog :pedomustdie: likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 15-Oct-2024 01:56:21 JST 

     in reply to

     • :blank:
     • ♡ miss olivia ♡
     • feld
     @feld @i @olivia Indeed, the three posts mentioned in the issue are the same three posts that's pinned on affected actor's profile. Don't notice anything out of ordinary in his collection aside from said posts having shitton of emojis.
     † top dog :pedomustdie: likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 15-Oct-2024 01:59:41 JST 

     in reply to

     • :blank:
     • ♡ miss olivia ♡
     • feld
     @feld @i @olivia Profile is https://misskey.io/users/9mhsmldaly3m08ft, the issue mentions some transmogrifier error but I haven't gotten it when forcefetching all three posts.
   • feld (feld@friedcheese.us)'s status on Tuesday, 15-Oct-2024 01:59:42 JST feld

     in reply to

     • :blank:
     • ♡ miss olivia ♡
     @mint @i @olivia weird, why would it keep fetching them? can you confirm for me the profile so I can take a closer look?
     
     
     also the dupes shouldn't happen with latest develop branch, at least if it tried it would cancel inserting the job every time because a duplicate one existed (until pruner kicks in and clears up old Oban jobs)
   •  (mint@ryona.agency)'s status on Tuesday, 15-Oct-2024 02:09:34 JST 

     in reply to

     • :blank:
     • ♡ miss olivia ♡
     • feld
     @feld @i @olivia The exact error might be irrelevant since they might also have some geoblocks or other :cloudflare: shenanigans going. What's more concerning is pileup happening in a first place; now that I'm thinking about it might be recursion.
     1. pleromer receives an activity referencing that guy's profile/post
     2. it fetches them
     3. fetch pipeline kicks in
     4. pinned posts fetching happens as a part of pipeline
     5. pleromer inserts RemoteFetcherWorker jobs for those posts
     6. said jobs try to fetch pinned posts again
     If that's the case (too lazy to confirm, sorry) and fetcher jobs start erroring out, the queue raises exponentially. Hopefully not?
   •  (mint@ryona.agency)'s status on Tuesday, 15-Oct-2024 02:10:07 JST 

     in reply to

     • :blank:
     • ♡ miss olivia ♡
     • feld
     @feld @i @olivia Yeah, misskey uses flakes in their AP actor IDs.
   • feld (feld@friedcheese.us)'s status on Tuesday, 15-Oct-2024 02:10:08 JST feld

     in reply to

     • :blank:
     • ♡ miss olivia ♡
     @mint @i @olivia that redirects me to an account named beer_bastard. Same?
   • feld (feld@friedcheese.us)'s status on Tuesday, 15-Oct-2024 02:12:20 JST feld

     in reply to

     • :blank:
     • ♡ miss olivia ♡
     @mint @i @olivia
     
     > 5. pleromer inserts RemoteFetcherWorker jobs for those posts
     
     these inserts were not set to be unique, but they are now
      likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 15-Oct-2024 02:14:52 JST 

     in reply to

     • :blank:
     • ♡ miss olivia ♡
     • feld
     @feld @i @olivia Indeed, but that's more of last frontier measure. There would still be some friction left pertaining to checking whether such job exists and raising an exception if it does.
   • feld (feld@friedcheese.us)'s status on Tuesday, 15-Oct-2024 02:19:48 JST feld

     in reply to

     • :blank:
     • ♡ miss olivia ♡
     @mint @i @olivia you don't want to raise an exception on a duplicate job in Oban; that would break a lot of stuff needlessly. It just drops the job silently. It's not an error scenario that needs to raise / cause the process to abort.
      likes this.
   • Vaghrad (vaghrad@asphodel.rip)'s status on Tuesday, 15-Oct-2024 21:13:55 JST Vaghrad

     in reply to

     • :blank:
     • ♡ miss olivia ♡
     • feld
     @mint @i @feld @olivia found this post by searching for the beer bastard guy, guess that explains why my cpu was cooking itself to death the past few days :FF_Bomb:
     implementing https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4253/diffs?commit_id=a887188890a6b8c9e97c6cafe1776bb151e63843 from this thread and deleting the stuck oban jobs seems to have fixed it for now, thank you guys
      likes this.