continuwuation/continuwuity
continuwuation/continuwuity
15
94
Fork 107
Code Issues 127 Pull requests 21 Releases 30 Packages 3 Activity Actions 12

docs: Explain how to enable sending admin commands to the server console for docker deployments #1553

Manually merged
Jade merged 6 commits from ky-bean/continuwuity:docker-admin-console into main 2026-04-23 20:05:35 +00:00
Conversation 11 Commits 6 Files changed 3 +22 -1
ky-bean commented 2026-03-19 21:23:55 +00:00
Contributor
Copy link

This pull request adds a note to the Admin Command Reference page of the docs adding info about how docker deployments should be setup to enable correctly attaching to the server's console, which then enables sending admin commands to the server console as expected.

The only open question I have regarding this is whether or not the -it / std_open: true & tty: true changes for docker should be included by default in the docker deployment docs. There could be an argument about system security being at risk with the server's console tty being available to any user with permissions to run docker attach but that's not something I'm experienced with determining how much that might be an issue.

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 pull request adds a note to the Admin Command Reference page of the docs adding info about how docker deployments should be setup to enable correctly attaching to the server's console, which then enables sending admin commands to the server console as expected. The only open question I have regarding this is whether or not the `-it` / `std_open: true` & `tty: true` changes for docker should be included by default in the docker deployment docs. There could be an argument about system security being at risk with the server's console tty being available to any user with permissions to run `docker attach` but that's not something I'm experienced with determining how much that might be an issue. <!-- 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. - [x] 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
ky-bean force-pushed docker-admin-console from 114b935c9f
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Details
to fd062a7bf0
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 3m0s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 13m16s
Details
2026-03-19 21:24:25 +00:00 Compare
lveneris commented 2026-03-20 12:34:35 +00:00
Contributor
Copy link

I think most of this guidance should go in the Docker deployment docs, since it's Docker specific. Maybe there should be a warning on one of the pages that you need to add those options in order to use the admin console. You can then link back to that from the admin commands reference, wth a note like this:

To enable this for Docker deployments, see [the guide](<link>), after which you can use `docker attach` to send commands to the admin console.

Much less noise for people the advice isn't relevant to, in my humble opinion.

I think most of this guidance should go in the Docker deployment docs, since it's Docker specific. Maybe there should be a warning on one of the pages that you need to add those options in order to use the admin console. You can then link back to that from the admin commands reference, wth a note like this: ```md To enable this for Docker deployments, see [the guide](<link>), after which you can use `docker attach` to send commands to the admin console. ``` Much less noise for people the advice isn't relevant to, in my humble opinion.
👍 1
ky-bean commented 2026-03-20 20:36:33 +00:00
Author
Contributor
Copy link

@lveneris I went back n forth on where I thought the comment should go, linking in the admin reference to the docker docs makes sense, I'll make that change!

@lveneris I went back n forth on where I thought the comment should go, linking in the admin reference to the docker docs makes sense, I'll make that change!
ky-bean force-pushed docker-admin-console from fd062a7bf0
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 3m0s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 13m16s
Details
to 64e025a8d4
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Details
2026-03-20 20:37:53 +00:00 Compare
lveneris requested changes 2026-03-22 11:41:12 +00:00
Dismissed
docs/deploying/docker.mdx Outdated
@ -254,1 +254,4 @@
## Accessing the Server's Console
In order to enable access the server's console to [send admin commands](../reference/admin/index.md) from the CLI, the docker deployment will need to be made interactive and allocate a psuedo-tty. For deployments via Docker Compose, this means adding `stdin_open: true` and `tty: true` to the containers decleration:
lveneris commented 2026-03-22 11:29:44 +00:00
Contributor
Copy link

You missed a "to" between "access the", but I would propose changing the structure of this.

Some notes for your reference, since I don't really like to throw suggestions at people without giving them anything to learn from:

  • "In order to" is redundant and "To" should usually be preferred
  • The passive voice is not ideal for instructional documents; be as direct as possible
  • Consistency is important, "Docker" should be capitalized everywhere
  • "the containers declaration" should be "the container's declaration"

With that in mind, here is my proposal:

Before you can access the server's console and [send admin commands](../reference/admin/index.md) from the CLI, you need to make the container interactive and allocate a pseudo-tty. For Docker Compose deployments, this means enabling `stdin_open` and `tty` in the container's declaration:

You could also split off the last sentence into its own paragraph, to be consistent with the separation for the docker run method.

You missed a "to" between "access the", but I would propose changing the structure of this. Some notes for your reference, since I don't really like to throw suggestions at people without giving them anything to learn from: - "In order to" is redundant and "To" should usually be preferred - The passive voice is not ideal for instructional documents; be as direct as possible - Consistency is important, "Docker" should be capitalized everywhere - "the containers declaration" should be "the container's declaration" With that in mind, here is my proposal: ``` Before you can access the server's console and [send admin commands](../reference/admin/index.md) from the CLI, you need to make the container interactive and allocate a pseudo-tty. For Docker Compose deployments, this means enabling `stdin_open` and `tty` in the container's declaration: ``` You could also split off the last sentence into its own paragraph, to be consistent with the separation for the `docker run` method.
ky-bean commented 2026-03-23 01:50:46 +00:00
Author
Contributor
Copy link

Thank you for taking the time to provide constructive criticism, I definitely don't write documentation enough (or really do much writing at all..) I appreciate receiving the guidance on the right language to use and how to construct Actually Helpful documentation!

Thank you for taking the time to provide constructive criticism, I definitely don't write documentation enough (or really do much writing at all..) I appreciate receiving the guidance on the right language to use and how to construct Actually Helpful documentation!
ky-bean marked this conversation as resolved
docs/deploying/docker.mdx Outdated
@ -255,0 +261,4 @@
homserver:
stdin_open: true
tty: true
<snip>
lveneris commented 2026-03-22 11:32:32 +00:00
Contributor
Copy link

Preferably this should be replaced with something like

# ...

or

# The rest of your declaration goes here

since comments are preferred for elision

Preferably this should be replaced with something like ```yaml # ... ``` or ```yaml # The rest of your declaration goes here ``` since comments are preferred for elision
ky-bean marked this conversation as resolved
docs/deploying/docker.mdx Outdated
@ -255,0 +266,4 @@
If you choose to deploy via `docker run`, then add the flags `-i`/`--interactive` and `-t`/`--tty` to the command.
From there you can access the server's console by running `docker attach <container-name>`, which will show the server\'s prompt `uwu> `. To exit `docker attach` press ctrl+p then ctrl+q.
lveneris commented 2026-03-22 11:38:57 +00:00
Contributor
Copy link

Was server\'s meant to be escaped? This does not appear anywhere else.

I am also not sure of any existing precedent for the style of writing keybinds into the docs, but deferring to the Docker docs page, it would make sense to capitalize the CTRL and put them in inline code segments at least.

I might be inclined to suggest

Note that using `CTRL+c` will stop the container. To exit `docker attach`, press `CTRL+p` then `CTRL+q`.
Was `server\'s` meant to be escaped? This does not appear anywhere else. I am also not sure of any existing precedent for the style of writing keybinds into the docs, but deferring to [the Docker docs page](https://docs.docker.com/reference/cli/docker/container/attach), it would make sense to capitalize the CTRL and put them in inline code segments at least. I might be inclined to suggest ``` Note that using `CTRL+c` will stop the container. To exit `docker attach`, press `CTRL+p` then `CTRL+q`.
ky-bean commented 2026-03-23 00:20:30 +00:00
Author
Contributor
Copy link

Regarding the escaped single-quote, I think my brain probably just crossed some wires and thought I was writing the backtick and needed to escape it to render correctly in markdown, it can be removed.

Regarding the escaped single-quote, I think my brain probably just crossed some wires and thought I was writing the backtick and needed to escape it to render correctly in markdown, it can be removed.
ky-bean commented 2026-03-23 00:30:57 +00:00
Author
Contributor
Copy link

Ah, going back in and editing the docs I realize now why I escaped the quote mark, because these files have '.mdx' extensions my editor wasn't registering them as markdown files and so the single quotes were being interpreted as a string by the code highlighter.

Ah, going back in and editing the docs I realize now why I escaped the quote mark, because these files have '.mdx' extensions my editor wasn't registering them as markdown files and so the single quotes were being interpreted as a string by the code highlighter.
ky-bean marked this conversation as resolved
docs/reference/admin/index.md Outdated
@ -8,3 +8,3 @@
* All commands listed here may be used by server administrators in the admin room by sending them as messages.
* If the `admin_escape_commands` configuration option is enabled, server administrators may run certain commands in public rooms by prefixing them with a single backslash. These commands will only run on _their_ homeserver, even if they are a member of another homeserver's admin room. Some sensitive commands cannot be used outside the admin room and will return an error.
* All commands listed here may be used in the server's console, if it is enabled. Commands entered in the console do not require the `!admin` prefix.
* All commands listed here may be used in the server's console, if it is enabled. Commands entered in the console do not require the `!admin` prefix. If continuwuity is deployed via docker be sure to set the appropriate options detailed in [the docker deployment guide](../../deploying/docker.mdx#accessing-the-servers-console) to enable access to the server's console.
lveneris commented 2026-03-22 11:40:49 +00:00
Contributor
Copy link

Continuwuity and Docker should be capitalized here, and there should be a comma on "via Docker, be sure".

Continuwuity and Docker should be capitalized here, and there should be a comma on "via Docker, be sure".
ky-bean marked this conversation as resolved
ky-bean force-pushed docker-admin-console from 438fc8aecb
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Details
to 7a8e108589
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Details
2026-03-23 00:23:07 +00:00 Compare
ky-bean commented 2026-03-23 02:15:32 +00:00
Author
Contributor
Copy link

@lveneris I've updated following your suggestions, thanks again for the reviews!

@lveneris I've updated following your suggestions, thanks again for the reviews!
❤️ 1
lveneris approved these changes 2026-03-23 06:50:04 +00:00
Dismissed
Jade reviewed 2026-03-27 19:28:01 +00:00
docs/deploying/docker.mdx Outdated
@ -255,0 +270,4 @@
From there you can access the server's console by running `docker attach <container-name>`, which will show the server's prompt `uwu> `.
Note that using `CTRL+c` within `docker attach`'s context will forward the signal to the server, stopping it. To exit `docker attach` press `CTRL+p` then `CTRL+q`. See [Docker's reference](https://docs.docker.com/reference/cli/docker/container/attach/) for more information.
Jade commented 2026-03-27 19:28:01 +00:00
Owner
Copy link

At least on podman, this forwards to the container but opens the console as expected. Does docker do weird things here? stopping the server should be triggered by ctrl+/ iirc

At least on podman, this forwards to the container but opens the console as expected. Does docker do weird things here? stopping the server should be triggered by ctrl+/ iirc
ky-bean commented 2026-03-27 19:35:09 +00:00
Author
Contributor
Copy link

I'm not entirely sure what you're asking about here... The instructions as written work for plain docker deployments, I can access the container's console and send admin commands as intended, and the sequence CTRL+P CTRL-Q exits the attached session. CTRL+C will shutdown the server bc SIGINT is forwarded through the attachment to the server process (or the console process if it's seperate). CTRL+C is mentioned here because the naive person (AKA me before looking it up) will try to use CTRL+C to exit the attached session, and will be left with surprise downtime instead.

I'm not entirely sure what you're asking about here... The instructions as written work for plain docker deployments, I can access the container's console and send admin commands as intended, and the sequence CTRL+P CTRL-Q exits the attached session. CTRL+C will shutdown the server bc SIGINT is forwarded through the attachment to the server process (or the console process if it's seperate). CTRL+C is mentioned here because the naive person (AKA me before looking it up) will try to use CTRL+C to exit the attached session, and will be left with surprise downtime instead.
Jade commented 2026-03-27 19:43:53 +00:00
Owner
Copy link

In which case, yes, docker is messing with intended behaviour

In which case, yes, docker is messing with intended behaviour
screen-20260327-194316.mp4
2.2 MiB
ky-bean commented 2026-03-27 23:44:57 +00:00
Author
Contributor
Copy link

Is there anything you'd recommend I add to clarify this discrepancy?

Is there anything you'd recommend I add to clarify this discrepancy?
ky-bean force-pushed docker-admin-console from c9e29937db
Some checks failed
Check Changelog / Check for changelog (pull_request_target) Successful in 10s
Details
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Details
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m49s
Details
to 357d9191e3
Some checks failed
Check Changelog / Check for changelog (pull_request_target) Successful in 9s
Details
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Details
2026-03-28 02:21:05 +00:00 Compare
chore: Add news fragment for #1553
Some checks failed
Check Changelog / Check for changelog (pull_request_target) Successful in 10s
Details
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Details
b5e46b439e
ginger reviewed 2026-03-29 16:19:40 +00:00
docs/deploying/docker.mdx Outdated
@ -254,1 +254,4 @@
## Accessing the Server's Console
Before you can access the server's console and [send admin commands](../reference/admin/index.md) from the CLI, you will need to make the container interactive and allocate a pseudo-tty.
ginger commented 2026-03-29 16:19:40 +00:00
Owner
Copy link

Might be worth noting that the console won't open by default unless admin_console_automatic is true in the config

Might be worth noting that the console won't open by default unless `admin_console_automatic` is `true` in the config
ky-bean commented 2026-03-30 10:04:06 +00:00
Author
Contributor
Copy link

Good point! I've added a note detailing that at the end of that first paragraph.

Good point! I've added a note detailing that at the end of that first paragraph.
ginger marked this conversation as resolved
docs(docker): Add note for required config setting
All checks were successful
Check Changelog / Check for changelog (pull_request_target) Successful in 10s
Details
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m4s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 44m59s
Details
e3cf878630
lveneris approved these changes 2026-04-05 11:20:08 +00:00
stratself commented 2026-04-08 08:25:10 +00:00
Contributor
Copy link

@ky-bean, I'm opening #1594 which will likely override your additions in this PR. Ideally I'd like to include your changes somewhere in the new restructured page (if it's approved that is). I can add them myself and put you as Co-authored-by: and Co-committed-by: if that's okay

Maintainers please let us know how to coordinate.

@ky-bean, I'm opening #1594 which will likely override your additions in this PR. Ideally I'd like to include your changes somewhere in the new restructured page (if it's approved that is). I can add them myself and put you as `Co-authored-by:` and `Co-committed-by:` if that's okay Maintainers please let us know how to coordinate.
Jade commented 2026-04-13 15:28:26 +00:00
Owner
Copy link

@stratself if you want you can cherry-pick changes.

@stratself if you want you can cherry-pick changes.
👍 1
Jade referenced this pull request from a commit 2026-04-23 19:47:34 +00:00
chore: Add news fragment for #1553
Jade manually merged commit bd3944573b into main 2026-04-23 20:05:35 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Aranjedeath
lveneris
Labels
Clear labels   
Blocked
This pull request or issue is currently blocked from being merged/closed

  
Bug
Something isn't working as intended

  
Changelog
Added
 Changelog entry added

  
Changelog
Missing
 No changelog when one is needed

  
Changelog
None
 Changelog is unnecesary for this change

  
Cherry-picking
Commits picked from other conduit projects

  
Database
This requires or includes changes to the database

  
Dependencies
Something dependency related

  
Dependencies/Renovate
Automatic dependency upgrades by Renovate

  
Difficulty
Easy
 Low difficulty to implement - touches few parts of the codebase, low complexity

  
Difficulty
Hard
 High difficulty to implement - touches many parts of the codebase, high complexity

  
Difficulty
Medium
 Medium difficulty to implement - touches more parts of the codebase, higher complexity

  
Documentation
Improvements or additions to documentation

  
Enhancement
New feature or request

  
Good first issue
Good for newcomers

  
Help wanted
Additional eyes and keyboards are required for this one

  
Inherited
Issues that have been inhereted from the project pre-fork

  
Matrix/Administration
Features pertaining to homeserver administration

  
Matrix/Appservices
Features pertaining to the appservice API

  
Matrix/Auth
Features pertaining to authentication

  
Matrix/Client
Features pertaining to client-to-server interactions

  
Matrix/Core
Issues relating to core matrix functionality, such as state resolution and PDU formats

  
Matrix/E2EE
Issues related to end to end encryption

  
Matrix/Federation
Features pertaining to server-to-server interactions

  
Matrix/Hydra
Issues related to room version 12 and related changes (temporary label)

  
Matrix/MSC
Features pertaining to unstable matrix features

  
Matrix/Media
Features pertaining to media interactions

  
Matrix/T&S
Changes or issues related to trust & safety tooling

  
Merge
This PR is ready to be merged

  
Merge/Manual
This PR should be manually merged

  
Merge/Squash
This PR should be squashed when it is merged

  
Meta
Related to housekeeping, maintenance, or other repo-meta.

  
Meta/CI
Issues related to CI changes

  
Meta/Packaging
Packaging

  
Priority
Blocking
 This issue is blocking the next release

  
Priority
High
 This issue is very important

  
Priority
Low
 This issue is of a rather low priority

  
Security
This item is related to general security

  
Status
Confirmed
 This issue has enough information and is confirmed

  
Status
Duplicate
 This issue or pull request already exists

  
Status
Invalid
 This issue doesn't seem right

  
Status
Needs Investigation
 This issue needs further investigation

  
Support
Questions or support requests

  
Wont fix
This will not be worked on

  
old/ci/cd
Ci/CD

Archived

  
old/rust
Pull requests that update Rust code

Archived

No labels
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
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/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
Wont fix
old/ci/cd
old/rust
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 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!1553
No description provided.