[bug] Ghost Report #366
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#366
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
From source
Extra details
Ubuntu Linux
Version
3.4.0-197-ge3121b22
PostgreSQL version
14
What were you trying to do?
I am attempting close or resolve a report sent by an external instance (an instance which has since been added to the REJECT list, though this does not seem relevant as modifying MRF policies did not fix the issue).
What did you expect to happen?
The report should close or resolve gracefully. This bug does not happen with all reports; but it seems one got "stuck".
What actually happened?
When performing the action on the front-end moderation UI within PleromaFE, the report appears to disappear, but returns as active upon refresh. When doing so on AdminFE, the error "Request failed with status code 400 - not_found" is displayed.
Logs
No response
Severity
I cannot use it as easily as I'd like
Have you searched for this issue?