Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Container feature detection

未关闭
#656 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
go
领域
testing

调研方向

首先将此提案与 Complement issue 654 进行比较,尤其是比较其中建议的配置格式。定义 homeserver 如何声明对各项功能的支持,以及该声明如何在容器启动前启用或跳过单个测试。完成标准是该方案能够涵盖媒体删除、房间/历史记录删除以及每个测试的速率限制等示例,同时不要求重启正在运行的容器。

由索引模型根据 Issue 内容生成。

描述

There are an increasing set of features which are:

  • not in the spec
  • required in practice for all production homeservers.

A few examples:

  • ability to delete media.
  • ability to delete rooms/history entirely.
  • change rate limits for the CS API.

It would be nice if a homeserver could "declare" that it supports this, which then runs some magic command on the container to enable/disable this in the container prior to startup (to avoid needing to SIGHUP a running container or other nonsense). If this declaration API is standardised, it would allow the same rate limit tests to work across different HSes for example, and if not, it can be easily skipped.

This has overlap with https://github.com/matrix-org/complement/issues/654 which suggests a configuration format for saying which tests should be run. One can imagine that the "rate limit tests" were an MSC and hence could be opted-in to. The difference is that this needs configuration on a per-test basis, as we usually want very high rate limits in tests.

主要语言
Go
星标
100
派生
72
平均合并
3 天 19 小时
30 天内合并 PR
10

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

matrix-org/complement 的其他 Issue

查看 matrix-org/complement 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。