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

`river_job.max_attempts` (the database column) should have a default value of 25

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

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
go, postgresql
领域
database

调研方向

Start by locating the river_job schema and the next migration that changes it. Check how other columns define defaults, then verify that a raw SQL insert can omit max_attempts and receive 25; the change is done when the schema default is included in that migration.

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

描述

needs db migration

While writing documentation for how to insert a job using raw SQL, I came across the fact that while almost every river_job field gets a reasonable default, max_attempts is the odd man out and must have a value specified despite having a clear default of 25 in code.

Having a default on this column would be a slight improvement in that it'd make a manually inserted job a little easier to insert. Also, I think not having a default on this property may have been a mistake anyway since all other properties except the highly variable ones like kind and args have one.

Not worth its own migration, but let's ship the change opportunistically during the next migration that goes out.

主要语言
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 摘要。