eta
I'm pretty sure this one is actually PEBKAC -- I had hacked up my GtS database to move some of my old posts over from another instance, but this resulted...
I lied! I pinned a non-cursed toot, left it a while, and came back to another sea of constantly retrying Pleromas in the logs :c
It seems very linked to the pinned toot -- unpinning the toot will make the Pleromas stop looping, for example -- so I doubt that's it
I just updated my own patchset to HEAD actually, so I'll pin a toot and see if I can get some pleromas stuck in it again...
Update: It's 2 days later and I just opened my gts logs to find about 10 Pleroma requests per second, so this is still an issue! Please let me know...
It only affects sufficiently old Akkoma; modern Akkoma versions don't seem to have an issue.
That was originally the case, but the problem exists even with non-'imported' toots.
Very much so -- pinned a post today and came back an hour later to find GtS using all the CPU on the machine :(
Seems fixed! I've had a pinned post for 2 days and haven't seen the problem recur; additionally, the handy new HTTP header block thing makes this easy to mitigate without...
(whoops, didn't actually mean to instantly close, but I guess that's fine?)