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

Open the account command connections through dbkit/postgres

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with the two open calls named in the issue: pgxpool.New in stores.go and stdlib.OpenDB in schema.go, both under gonsole/auth/postgres. Reproduce the panic by running account:list with pool_health_check_period=0s, and the schema failure with a pool_ key in the address. Read dbkit/postgres to see how it takes a connection cap, since the issue asks that cap to be passed in by the app. Done when both stores open through dbkit under that cap, and both address cases no longer panic or fail.

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

描述

bug help wanted

What

gonsole/auth/postgres v0.2.0 opens its stores with pgxpool.New (stores.go) and its schema step with stdlib.OpenDB (schema.go). Open both through dbkit/postgres, under a connection cap the app passes in.

Why

  • These connections sit outside the app's own connection cap.
  • pool_health_check_period=0s in the address makes pgxpool.New panic with non-positive interval for NewTicker, so account:list exits 2 with a stack trace.
  • The schema step sends any pool_ key to the server, which stops with unrecognized configuration parameter. gouncer's authkit/postgres Migrate opens with sql.Open and does the same.
主要语言
Go
星标
69
派生
3
平均合并
9 小时 11 分钟
30 天内合并 PR
38

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

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

gopherium/framework 的其他 Issue

查看 gopherium/framework 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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