ban -> unban -> invite -> join is illegal in v12 rooms with a non-public
join rule, no matter who issues the first three #1093
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status/Blocked
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
To-Merge
Wont fix
old/ci/cd
old/rust
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity#1093
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The ban -> unban -> invite appears to be fine, but as soon as the invitee accepts the invite to the room, their join soft fails, and they remain in an invited state. It appears as if continuwuity is prioritising the
leave
membership caused by theunban
action over theinvite
one when checking the join against current state.State res trace logs attached. issue is not federation exclusive, the state does not resolve correctly on the origin server either.
nex referenced this issue2025-10-04 01:56:26 +00:00