feat: get-state-at admin command #1877

Merged
Jade merged 2 commits from 31a/continuwuity:pr-admin-get-state-at into main 2026-06-27 00:19:15 +00:00
Contributor

this PR add a debug get-state-at admin command to complement debug get-room-state

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:
<!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> this PR add a `debug get-state-at` admin command to complement `debug get-room-state` <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **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. <!-- 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
feat: get-state-at admin command
Some checks failed
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 2s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Failing after 4s
Checks / Prek / Check changed files (pull_request) Successful in 4s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m10s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
43be5410f6
chore: changelog
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Failing after 7s
Checks / Prek / Check changed files (pull_request) Successful in 8s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m57s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m12s
2d9e3894c8
Jade approved these changes 2026-06-26 01:24:26 +00:00
@ -506,1 +506,4 @@
#[admin_command]
pub(super) async fn get_state_at(&self, event_id: OwnedEventId) -> Result {
self.bail_restricted()?;
Owner

Probably not needed for this one, given it's a public fed endpoint. cc others if there's disagreement there?

Probably not needed for this one, given it's a public fed endpoint. cc others if there's disagreement there?
Author
Contributor

it's there for parity with get-room-state, although the only thing it guards against (in both functions) is accidentally pasting an ID from the wrong room, which is questionably necessary

it's there for parity with `get-room-state`, although the only thing it guards against (in both functions) is accidentally pasting an ID from the wrong room, which is questionably necessary
Owner

Fair enough

Fair enough
Jade marked this conversation as resolved
31a force-pushed pr-admin-get-state-at from 2d9e3894c8
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Failing after 7s
Checks / Prek / Check changed files (pull_request) Successful in 8s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m57s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m12s
to 8a3e2f348a
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Check changed files (pull_request) Successful in 7s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m2s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m46s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
2026-06-26 06:38:30 +00:00
Compare
Jade force-pushed pr-admin-get-state-at from 8a3e2f348a
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Check changed files (pull_request) Successful in 7s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m2s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m46s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
to 21e93f8feb
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Checks / Prek / Check changed files (pull_request) Successful in 4s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m4s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m49s
Checks / Prek / Check changed files (push) Successful in 7s
Checks / Prek / Pre-commit & Formatting (push) Successful in 1m1s
Documentation / Build and Deploy Documentation (push) Successful in 1m3s
Checks / Prek / Clippy and Cargo Tests (push) Successful in 9m49s
Release Docker Image / Build linux-amd64 (release) (push) Successful in 12m24s
Release Docker Image / Build linux-arm64 (release) (push) Successful in 9m27s
Release Docker Image / Create Multi-arch Release Manifest (push) Successful in 18s
Release Docker Image / Build linux-amd64 (max-perf) (push) Successful in 30m3s
Release Docker Image / Build linux-arm64 (max-perf) (push) Successful in 26m5s
Release Docker Image / Release Binaries (push) Has been skipped
Release Docker Image / Create Max-Perf Manifest (push) Successful in 18s
Release Docker Image / Mirror Images (push) Successful in 2m11s
2026-06-27 00:09:12 +00:00
Compare
Jade scheduled this pull request to auto merge when all checks succeed 2026-06-27 00:09:50 +00:00
Jade merged commit 21e93f8feb into main 2026-06-27 00:19:15 +00:00
Jade deleted branch pr-admin-get-state-at 2026-06-27 00:19:16 +00:00
ginger added this to the 26.6.0 milestone 2026-07-04 15:57:29 +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!1877
No description provided.