Yeah ok confirmed this is cause we've got data in the source tables that isn't included in the materialized view properly. Some Scylla wonkiness emerging from running our cluster in a split state right now. Hopefully we can sort it out early this week. The data is indexed, just misbehaving views.
We had a DB node that was unhappy and left the cluster over the weekend. I brought it back up and ran a repair, looks like the materialized views are happy now. @em.vg wanna check those threads now to see if they show replies properly? I'm seeing them from the API now :)
Some of that could be content from accounts that are taken down but haven't had their writes unwound. In this case could you still see the replies somewhere else (i.e. in notifications)?
nah I couldn't see it in notifications, but it was pretty soon after posting, so im not sure why an account would get banned that quick unless it posted 1000/s
this is actually very common, a ton of our automation comes after users perform actions on their account. if actions are determined to be likely suspicious, they’ll either get labeled or taken down based on confidence
(Clearly some alarms that need tuning that got muted during the migration since there's been a lot of node churn as we upgrade versions and add new machines etc.)
Comments
(ty for fixing!)
confirmed they are now displaying properly
atprotocol is saved (tyvm)