-
Notifications
You must be signed in to change notification settings - Fork 27
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
Deleting a room seems to succeed, but the room remains #145
Comments
We would definitely say in synadm that you can check on the room deletion status, and that deletion with the v2 API is not immediate and asynchronous. |
I've updated
Does that help clarify things? Previous:
|
Yes, that wording will be helpful for future users, I guess. Thank you for your quick response! |
After one of my users joined the matrixhq-Room the database space requirements started to expand rapidly. Thus, I decided to remove and block this room:
The call resulted in a loooong list of room members, which I acknowledged. The final message of the call was this:
Thus, I assumed that the room was gone.
But in fact it is still here and it still contains one of our local users:
Now I am confused.
I assumed, that the
synadm room delete
command would remove the local user from the room and delete the room (since it is not related to local users anymore).But this does not seem to happen.
Should I try to use the
--force-purge
option, even though there were no warnings or errors emitted during theroom delete
call?Thank you for your time!
Relevant software versions:
synadm
: 0.46matrix-synapse
: v1.99The text was updated successfully, but these errors were encountered: