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

Intermittent failure: `Test_Client_InsertNotificationsAreDeduplicatedAndDebounced`

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

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
go, postgresql
领域
databases, testing

调研方向

Start with Test_Client_InsertNotificationsAreDeduplicatedAndDebounced in client_test.go, especially the failure around lines 6289 and 6350. Run go test ./... -race -timeout 2m and use the linked CI run to compare the intermittent behavior. Done means the test no longer receives an insert notification while it should be debounced.

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

描述

Intermittent failure in Test_Client_InsertNotificationsAreDeduplicatedAndDebounced.

Sample run:
https://github.com/riverqueue/river/actions/runs/18163358692/job/51699168994?pr=1049

cd /home/runner/work/river/river && go test ./... -race -timeout 2m
--- FAIL: Test_Client_InsertNotificationsAreDeduplicatedAndDebounced (2.80s)
    client_test.go:6289: Reusing idle postgres schema "river_2025_10_01t13_15_00_schema_03" [user facing: "river_2025_10_01t13_15_00_schema_03"] after cleaning in 744.730859ms [4 generated] [3 reused]
    logger.go:256: time=2025-10-01T13:15:01.890Z level=INFO msg="River client started" client_id=runnervm3ublj_2025_10_01T13_15_01_338625
    logger.go:256: time=2025-10-01T13:15:01.890Z level=INFO msg="inserting queue1 job"
    logger.go:256: time=2025-10-01T13:15:01.979Z level=INFO msg="received notification" topic=river_insert payload="{\"queue\": \"queue1\"}"
    logger.go:256: time=2025-10-01T13:15:01.979Z level=INFO msg="inserting queue1 job"
    logger.go:256: time=2025-10-01T13:15:02.043Z level=INFO msg="inserting queue1 job"
    logger.go:256: time=2025-10-01T13:15:02.140Z level=INFO msg="inserting queue1 job"
    logger.go:256: time=2025-10-01T13:15:02.279Z level=INFO msg="inserting queue1 job"
    logger.go:256: time=2025-10-01T13:15:02.903Z level=INFO msg="inserting queue1 job"
    logger.go:256: time=2025-10-01T13:15:02.905Z level=INFO msg="received notification" topic=river_insert payload="{\"queue\": \"queue1\"}"
    client_test.go:6350: received insert notification when it should have been debounced {topic:river_insert payload:{Queue:queue1}}
    logger.go:256: time=2025-10-01T13:15:03.394Z level=INFO msg="River client stopped" client_id=runnervm3ublj_2025_10_01T13_15_01_338625
    riverdbtest.go:289: Checked in postgres schema "river_2025_10_01t13_15_00_schema_03"; 1 idle schema(s) [5 generated] [4 reused]
FAIL
FAIL	github.com/riverqueue/river	27.292s
主要语言
Go
星标
5.7k
派生
179
平均合并
2 天 19 小时
30 天内合并 PR
12

贡献指南

这个仓库没有索引到贡献指南

从这里开始

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

riverqueue/river 的其他 Issue

查看 riverqueue/river 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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