[bug] Emoji react does not disappear, shows 0 instead #584
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#584
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
Docker
Extra details
Arch linux building docker image from source
Version
8c956bc671
PostgreSQL version
14.8
What were you trying to do?
I deactivated a user for spamming and noticed their emoji reactions were still visible on posts, despite there being "0" users who have reacted.
What did you expect to happen?
Emoji reaction should not show up if there are 0 accounts listed.
What actually happened?
Emoji react is still visible even when no accounts have used it, after deactivating the person who put it on.
Logs
No response
Severity
I can manage
Have you searched for this issue?
I'm also having this issue. I underestimated the importance of blocking certain remote instances, and ended up having my instance get brigaded. The comments cleaned up fine, but the puke and laugh emoji reacts are plastered all over the place, unfortunately.
I've also noticed that from a refreshed page, it'll show the original number of users who reacted, and then only drop it down to zero on mouse-hover.
Even if it's a patch-work temporary solution, I'd love to know if there's a way to remove the affected emojis while waiting for the bug to get fixed.
so the reason this happens is that reactions are actually stored inline on the activity itself (don't ask, long story), so deactivating a user won't scrub reaction data, and it would be rather intensive to do it on demand
however adding cleanup to the objectv pruner scheduled task to take care of this is certainly doable I think
fixed via
8fe29bf5d2