feat: Exclude empty rooms from !admin rooms list by default #1386

Merged
Jade merged 2 commits from nex/feat/admin-hide-empty-rooms into main 2026-02-15 23:03:39 +00:00
Owner

Hides empty/disconnected rooms from !admin rooms list by default

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
Hides empty/disconnected rooms from `!admin rooms list` by default **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. - [ ] I have written a [news fragment][n1] for this PR, if applicable<!--(can be done after hitting open!)-->. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages [n1]: https://towncrier.readthedocs.io/en/stable/tutorial.html#creating-news-fragments
feat: Exclude empty rooms from !admin rooms list by default
Some checks failed
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
b51b68be9d
Reviewed-By: Ginger <ginger@gingershaped.computer>
nex requested reviews from Jade, ginger 2026-02-15 22:41:28 +00:00
@ -29,2 +30,4 @@
})
.then(|room_id| get_room_info(self.services, room_id))
.then(|(room_id, total_members, name)| async move {
let room_id2 = room_id.clone(); // this is so dumb
Author
Owner

This feels wrong, but the compiler won't let me re-use the room_id in the parameter if I borrow it foractive_local_users_in_room. Is there a more correct way?

This feels wrong, but the compiler won't let me re-use the `room_id` in the parameter if I borrow it for`active_local_users_in_room`. Is there a more correct way?
Owner
error[E0505]: cannot move out of `room_id` because it is borrowed
  --> src/admin/room/commands.rs:40:5
   |
32 |         .then(|(room_id, total_members, name)| async move {
   |                 ------- binding `room_id` declared here
...
37 |                 .active_local_users_in_room(&room_id)
   |                                             -------- borrow of `room_id` occurs here
...
40 |             (room_id, total_members, local_members.len(), name)
   |              ^^^^^^^                 ------------- borrow later used here
   |              |
   |              move out of `room_id` occurs here

This is caused by local_members.len() being after room_id, so you're trying to move room_id out of the scope of the function while it's still doing osmething. Why rust can't deal with that I have no damn idea

``` error[E0505]: cannot move out of `room_id` because it is borrowed --> src/admin/room/commands.rs:40:5 | 32 | .then(|(room_id, total_members, name)| async move { | ------- binding `room_id` declared here ... 37 | .active_local_users_in_room(&room_id) | -------- borrow of `room_id` occurs here ... 40 | (room_id, total_members, local_members.len(), name) | ^^^^^^^ ------------- borrow later used here | | | move out of `room_id` occurs here ``` This is caused by local_members.len() being after room_id, so you're trying to move room_id out of the scope of the function while it's still doing osmething. Why rust can't deal with that I have no damn idea
nex marked this conversation as resolved
refactor: Drop duplicate clone
Some checks are pending
Documentation / Build and Deploy Documentation (pull_request) Waiting to run
Checks / Prek / Pre-commit & Formatting (pull_request) Waiting to run
Checks / Prek / Clippy and Cargo Tests (pull_request) Waiting to run
93ca1a52dc
Jade approved these changes 2026-02-15 23:00:03 +00:00
Jade force-pushed nex/feat/admin-hide-empty-rooms from 93ca1a52dc
Some checks are pending
Documentation / Build and Deploy Documentation (pull_request) Waiting to run
Checks / Prek / Pre-commit & Formatting (pull_request) Waiting to run
Checks / Prek / Clippy and Cargo Tests (pull_request) Waiting to run
to 38bf1ccbcc
Some checks failed
Documentation / Build and Deploy Documentation (push) Waiting to run
Checks / Prek / Pre-commit & Formatting (push) Waiting to run
Checks / Prek / Clippy and Cargo Tests (push) Waiting to run
Release Docker Image / Build linux-amd64 (release) (push) Waiting to run
Release Docker Image / Build linux-arm64 (release) (push) Waiting to run
Release Docker Image / Create Multi-arch Release Manifest (push) Blocked by required conditions
Release Docker Image / Build linux-amd64 (max-perf) (push) Blocked by required conditions
Release Docker Image / Build linux-arm64 (max-perf) (push) Blocked by required conditions
Release Docker Image / Create Max-Perf Manifest (push) Blocked by required conditions
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m15s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m6s
Checks / Prek / Clippy and Cargo Tests (pull_request) Failing after 31m24s
2026-02-15 23:03:30 +00:00
Compare
Jade merged commit 38bf1ccbcc into main 2026-02-15 23:03:39 +00:00
ginger added this to the next milestone 2026-02-20 14:11:16 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!1386
No description provided.