Summary

If user A blocks user B, user B will still appear in the group-feed of user A.

Steps to reproduce

Unknown - it appears to happen rarely, but very randomly.

I have seen multiple reports and I and other team members have seen it happen first-hand.

Platform information

Cross-platform web.

What is the current bug behavior?

Blocked users show up in feeds.

What is the expected correct behavior?

Blocked users should not appear for the blocker.

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

/label ~"T - Bug" ~"S - Triage:new"

Let's make sure

• Banned users disappear from the UI on feeds
• Banned users do not appear on reload
• We need to make sure that admins can only see blocked users by explicitly going to their channel page. They should not be showing up in anyone's feeds.

added scoped labels

changed the description

added scoped label

This probably extends out to other feeds as I've seen reports of that, however I've only seen it in groups also.

added scoped label

added scoped label

assigned to @benhayward.ben

added scoped label and automatically removed label

added scoped label and automatically removed label

removed label

changed milestone to %Sprint:01/29 Abatic Aenome

changed due date to February 11, 2020

changed weight to 4

changed time estimate to 4h

added scoped label and automatically removed label

added scoped label

removed due date

added scoped label and automatically removed label

changed the description

@benhayward.ben Updated this case with some action items to help get to the bottom of this one

@brianhatchet what are we wanting to do here? I'm in favour of adding safety nets either at engine level. I will take some time to investigate it but I think the nature of this issue makes it incredibly difficult to capture.

The Feeds repositories should filter this all out. I wonder if there are some ElasticSearch failures at work.