Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

team syncer leaves/joins puppets to channels every other bridge restart #661

Open
olmari opened this issue Feb 10, 2022 · 4 comments
Open

team syncer leaves/joins puppets to channels every other bridge restart #661

olmari opened this issue Feb 10, 2022 · 4 comments
Labels
S-Critical Prevents work, causes data loss, affects many users, and/or has no workaround. T-Defect Bugs, crashes, hangs, vulnerabilities, or other reported problems.

Comments

@olmari
Copy link

olmari commented Feb 10, 2022

Describe the bug
No matter what team_sync configuration settings are tried, latest bridge version leaves slack ghosts from linked channels on every "odd" bridge restart, and then joins them back on every "even" restart.

To Reproduce
Steps to reproduce the behavior:

  1. Enable team_sync for team, doesn't seem to matter how strict setup otherwise for syncer
  2. Restart bridge and observe slack ghosts joining synced room
  3. Restart bridge again and observe slack ghosts leaving synced room

Expected behavior
Bridge not kicking all synced users out from rooms after restart.
@olmari
Copy link
Author

olmari commented Feb 10, 2022 •
edited
Loading

This does not happend on 1.8.0.

@felixx9
Copy link

felixx9 commented Feb 14, 2022

I also see lots of leaves, when restarting. Didn't figure out a pattern, though.

@Half-Shot Half-Shot added S-Critical Prevents work, causes data loss, affects many users, and/or has no workaround. T-Defect Bugs, crashes, hangs, vulnerabilities, or other reported problems. labels May 13, 2022
@olmari olmari mentioned this issue Jan 13, 2023
Open
@ayushin
Copy link

ayushin commented Jul 15, 2023

anybody is working on this?

@olmari
Copy link
Author

olmari commented Jul 31, 2023

This is still the show stopper that keeps me updating to anything past 1.8.0 :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
S-Critical Prevents work, causes data loss, affects many users, and/or has no workaround. T-Defect Bugs, crashes, hangs, vulnerabilities, or other reported problems.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Half-Shot @olmari @ayushin @felixx9