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.

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

MPS Follow Up: MemberBanSynchronisationProtection seems to repeatedly detect previously banned members #337

Closed
Gnuxie opened this issue Apr 12, 2024 · 0 comments · Fixed by #347
Labels
blocks release used in exceptional circumstances when the `latest` tag would break L5 All Users Likelihood MPS Follow Up P2 Aggravating Priority level T4 Minor usability Impairs usability in secondary scenarios.

Comments

@Gnuxie
Copy link
Member

Gnuxie commented Apr 12, 2024

image

It doesn't go as far as recalling /ban but still, i'm not sure why the membership state isn't being updated in a way that would stop the protection from trying.

@Gnuxie Gnuxie added L5 All Users Likelihood P2 Aggravating Priority level T4 Minor usability Impairs usability in secondary scenarios. MPS Follow Up blocks release used in exceptional circumstances when the `latest` tag would break labels Apr 12, 2024
Gnuxie added a commit that referenced this issue Apr 16, 2024
* Update for MPS 0.17.1.

Part of #333
And #345

Fixes #337

* Add loggableConfigTracker to Draupnir.

Part of #217.
I don't think this is right yet.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocks release used in exceptional circumstances when the `latest` tag would break L5 All Users Likelihood MPS Follow Up P2 Aggravating Priority level T4 Minor usability Impairs usability in secondary scenarios.
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

1 participant