You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 26, 2022. It is now read-only.
Someone reported that forget looked stuck for them, upon investigation it had backed off really hard because every time it tried to delete a post, the server returned 404.
While it is possible for a post to vanish before we delete it, forget always refreshes immediately before a delete so the time period where it would have to happen is very small, and it wouldn't happen for every post. In my investigation, the posts did exist, up until forget tried to delete them. I don't know if the deletes went through.
The server in question is running Pleroma 2.3.0-167-g4912fc2f-production, and my gut feeling is that it is a Pleroma issue or even an instance-modification issue because I have never seen this before.
The text was updated successfully, but these errors were encountered:
Someone reported that forget looked stuck for them, upon investigation it had backed off really hard because every time it tried to delete a post, the server returned 404.
While it is possible for a post to vanish before we delete it, forget always refreshes immediately before a delete so the time period where it would have to happen is very small, and it wouldn't happen for every post. In my investigation, the posts did exist, up until forget tried to delete them. I don't know if the deletes went through.
The server in question is running
Pleroma 2.3.0-167-g4912fc2f-production
, and my gut feeling is that it is a Pleroma issue or even an instance-modification issue because I have never seen this before.The text was updated successfully, but these errors were encountered: