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

Test failures when v12 rooms are the default

未关闭
  • 哪里不对？
#799 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
冷清
技术栈
go
领域
testing-qa

调研方向

首先运行 tests/csapi 和 tests 下列出的失败测试，重点关注涉及 power levels、sync、房间创建和 federation 的用例。以 v12 房间作为默认值比较失败情况，并跟踪与 Complement federation server 的交互。当列出的失败在 v12 作为默认房间版本时全部通过，即表示完成。

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

描述

Failing tests on v12

tests/csapi

Most of these tests directly do something with PLs causing them to break. Some weird quirks with sync though need investigation.

--- FAIL: TestRoomDeleteAlias (8.40s)
    --- FAIL: TestRoomDeleteAlias/Parallel (0.00s)
        --- FAIL: TestRoomDeleteAlias/Parallel/Users_with_sufficient_power-level_can_delete_other's_aliases (0.70s)
        --- FAIL: TestRoomDeleteAlias/Parallel/Regular_users_can_add_and_delete_aliases_when_m.room.aliases_is_restricted (0.88s)

--- FAIL: TestRoomMembers (8.35s)
    --- FAIL: TestRoomMembers/Parallel (0.00s)
        --- FAIL: TestRoomMembers/Parallel/Test_that_we_can_be_reinvited_to_a_room_we_created (0.52s)

--- FAIL: TestDemotingUsersViaUsersDefault (7.36s)

--- FAIL: TestPowerLevels (7.51s)
    --- FAIL: TestPowerLevels/GET_/rooms/:room_id/state/m.room.power_levels_can_fetch_levels (0.01s)
    --- FAIL: TestPowerLevels/PUT_/rooms/:room_id/state/m.room.power_levels_can_set_levels (0.02s)
    --- FAIL: TestPowerLevels/PUT_power_levels_should_not_explode_if_the_old_power_levels_were_empty (0.01s)

--- FAIL: TestRoomCreationReportsEventsToMyself (12.77s)
    --- FAIL: TestRoomCreationReportsEventsToMyself/parallel (0.00s)
        --- FAIL: TestRoomCreationReportsEventsToMyself/parallel/Room_creation_reports_m.room.create_to_myself (0.12s)

--- FAIL: TestSync (20.19s)
    --- FAIL: TestSync/parallel (2.87s)
        --- FAIL: TestSync/parallel/sync_should_succeed_even_if_the_sync_token_points_to_a_redaction_of_an_unknown_event (10.18s)

--- FAIL: TestSyncTimelineGap (18.62s)
    --- FAIL: TestSyncTimelineGap/incremental (5.12s)
    --- FAIL: TestSyncTimelineGap/full (5.16s)
tests

Basically any test that uses the complement federation server is likely to be affected by this.

--- FAIL: TestIsDirectFlagFederation (7.66s)
--- FAIL: TestEventAuth (7.88s)
--- FAIL: TestFederationRedactSendsWithoutEvent (10.49s)
--- FAIL: TestInboundFederationRejectsEventsWithRejectedAuthEvents (13.96s)
--- FAIL: TestGetMissingEventsGapFilling (13.77s)
--- FAIL: TestOutboundFederationIgnoresMissingEventWithBadJSONForRoomVersion6 (8.16s)
--- FAIL: TestOutboundFederationEventSizeGetMissingEvents (8.14s)
--- FAIL: TestJoinViaRoomIDAndServerName (8.97s)
--- FAIL: TestJoinFederatedRoomWithUnverifiableEvents (7.96s)
    --- FAIL: TestJoinFederatedRoomWithUnverifiableEvents//send_join_response_missing_signatures_shouldn't_block_room_join (0.00s)
    --- FAIL: TestJoinFederatedRoomWithUnverifiableEvents//send_join_response_with_bad_signatures_shouldn't_block_room_join (0.00s)
    --- FAIL: TestJoinFederatedRoomWithUnverifiableEvents//send_join_response_with_unobtainable_keys_shouldn't_block_room_join (0.00s)
    --- FAIL: TestJoinFederatedRoomWithUnverifiableEvents//send_join_response_with_state_with_unverifiable_auth_events_shouldn't_block_room_join (0.00s)
--- FAIL: TestOutboundFederationSend (7.61s)
--- FAIL: TestNetworkPartitionOrdering (7.85s)
--- FAIL: TestSyncOmitsStateChangeOnFilteredEvents (8.16s)
--- FAIL: TestUnrejectRejectedEvents (7.92s)
主要语言
Go
星标
99
派生
72
平均合并
1 天 4 小时
30 天内合并 PR
8

环境准备

从这里开始

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

matrix-org/complement 的其他 Issue

查看 matrix-org/complement 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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