Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • Sign in / Register
Minds Backend - Engine
Minds Backend - Engine
  • Project overview
  • Repository
  • Issues 277
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 36
  • CI / CD
  • Security & Compliance
  • Packages
  • Analytics
  • Wiki
  • Snippets
  • Members
  • Collapse sidebar
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Minds
  • Minds Backend - EngineMinds Backend - Engine
  • Issues
  • #846

Closed
Open
Opened 4 months ago by Nicholas Lewis@javanick0 of 3 tasks completed0/3 tasks
Report abuse New issue

(bug): block does not work in groups

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.
Edited 4 days ago by Brian Hatchet

Linked issues
0

  • Discussion 3
  • Designs 0
  • Nicholas Lewis @javanick added Priority::1 - High Product::Groups Type::Bug scoped labels 4 months ago

    added scoped labels

  • Ben Hayward @benhayward.ben changed the description 2 months ago

    changed the description

  • Ben Hayward @benhayward.ben added Status::Scheduling scoped label 2 months ago

    added scoped label

  • Ben Hayward
    Ben Hayward @benhayward.ben · 2 months ago
    Developer

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

  • Brian Hatchet :speech_balloon: @brianhatchet added Sprint::01/01 - Xerothermic Xenarthra scoped label 1 month ago

    added scoped label

  • Brian Hatchet :speech_balloon: @brianhatchet added Squad::Blue scoped label 1 month ago

    added scoped label

  • Brian Hatchet :speech_balloon: @brianhatchet assigned to @benhayward.ben 1 month ago

    assigned to @benhayward.ben

  • Brian Hatchet :speech_balloon: @brianhatchet added Sprint::01/15 - Youthful Yabby scoped label and automatically removed Sprint::01/01 - Xerothermic Xenarthra label 1 month ago

    added scoped label and automatically removed label

  • Brian Hatchet :speech_balloon: @brianhatchet added Squad::Yellow scoped label and automatically removed Squad::Blue label 1 month ago

    added scoped label and automatically removed label

  • Brian Hatchet :speech_balloon: @brianhatchet removed Sprint::01/15 - Youthful Yabby label 1 month ago

    removed label

  • Brian Hatchet :speech_balloon: @brianhatchet changed milestone to %Sprint:01/29 Abatic Aenome 3 weeks ago

    changed milestone to %Sprint:01/29 Abatic Aenome

  • Brian Hatchet :speech_balloon: @brianhatchet changed due date to February 11, 2020 3 weeks ago

    changed due date to February 11, 2020

  • Brian Hatchet :speech_balloon: @brianhatchet changed weight to 4 3 weeks ago

    changed weight to 4

  • Brian Hatchet :speech_balloon: @brianhatchet changed time estimate to 4h 3 weeks ago

    changed time estimate to 4h

  • Brian Hatchet :speech_balloon: @brianhatchet added Status::Backlog scoped label and automatically removed Status::Scheduling label 3 weeks ago

    added scoped label and automatically removed label

  • Brian Hatchet :speech_balloon: @brianhatchet added Sprint::01/29 Abatic Aenome scoped label 3 weeks ago

    added scoped label

  • Brian Hatchet :speech_balloon: @brianhatchet removed due date 1 week ago

    removed due date

  • Brian Hatchet :speech_balloon: @brianhatchet added Sprint::02/12 - Baritone Baboon scoped label and automatically removed Sprint::01/29 Abatic Aenome label 4 days ago

    added scoped label and automatically removed label

  • Brian Hatchet :speech_balloon: @brianhatchet changed the description 4 days ago

    changed the description

  • Brian Hatchet
    Brian Hatchet :speech_balloon: @brianhatchet · 4 days ago
    Developer

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

  • Ben Hayward
    Ben Hayward @benhayward.ben · 1 day ago
    Developer

    @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.

Please register or sign in to reply
Assignee
Ben Hayward's avatar
Ben Hayward @benhayward.ben
none
Epic
None
Sprint::01/29 Abatic Aenome
Milestone
Sprint::01/29 Abatic Aenome
Time tracking
Estimated: 4h
None
Due date
None
6
Labels
Priority::1 - High Product::Groups Sprint::02/12 - Baritone Baboon Squad::Yellow Status::Backlog Type::Bug
4
Weight
4
Confidentiality
Not confidential
Lock issue
Unlocked
3
3 participants
user avatar
user avatar
user avatar
Reference: minds/engine#846