Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

The database connection pool is unconfigured and unmeasured

クローズ
  • 何か問題がありますか？
#339 コメント 4 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 3 日以内に返信

@Stanley471 がすでに取り組んでいます。

2026年10月16日 から。

  • #467 @sparkysolutions10-pixel による — オープン
  • #518 @Stanley471 による — オープン

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
45/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
nodejs, postgresql, prometheus, typescript
領域
databases, observability

調査の方向性

Start with where the Prisma client is constructed under src/ and the datasource config in prisma/, then check src/alerts/delivery.ts for the existing AbortSignal.timeout convention. Find where the Prometheus registry is set up so the pool metrics join it, and add the new variables to .env.example and the README. Done means the pool size and timeout are configurable with an arithmetic comment, exhaustion logs and counts a distinct error, and a vitest test in src/__tests__/ asserts that error. Run it with npm test, not jest.

索引モデルが issue の本文から書いたものです。

説明

area:database difficulty:intermediate help wanted points:150 Stellar Wave
Background

Nothing in src/ or prisma/ sets connection_limit or pool_timeout, so
Prisma's defaults apply. Lens runs HTTP handlers, several ingester loops per
network and a retention worker in one process, all sharing one pool, and the
deployment runs more than one instance — so the real limit against Postgres is
the pool size multiplied by the instance count, which nobody has worked out.

When the pool is exhausted, requests queue inside Prisma and surface as slow
responses rather than as a pool problem, which is close to impossible to
diagnose from the outside.

What to build
  • Set the pool size and the acquisition timeout explicitly, with a comment
    giving the arithmetic: pool × instances against the Postgres max_connections.
  • Export pool metrics — in use, idle, waiting — through the existing registry.
  • Make pool exhaustion diagnosable: a distinct log line and metric, not a generic
    timeout.
  • Note in the README that the ingesters and the API share a pool, since that is
    the surprising part.
Acceptance criteria
  • Pool size and timeout are explicit and configurable
  • A comment records the arithmetic against the database's connection limit
  • Pool utilisation is exported as a metric
  • Exhaustion produces a distinguishable error, asserted by a test
  • .env.example documents any new variables

Drips Wave · Complexity: Intermediate · 150 points

Repo: Divinity-Labs/Lens. Node + TypeScript, Fastify, Prisma on Postgres,
Redis for queues, Prometheus via prom-client.

Run the tests: npm test. The tests are vitest, not jest. Running jest
against this repo reports "66 suites, 0 tests" and means nothing. A single file
is npx vitest run src/__tests__/yourfile.test.ts.

Load test (prices) is already failing on main and has been for some
time. It is not your PR that broke it. Every other check should be green.

This service prices real assets on Stellar mainnet. A number that is wrong
is worse than a number that is missing, because a caller cannot tell the
difference. Prefer failing loudly over returning a plausible value.

Never elide an address, a contract id or a key in code, a comment or a test
fixture. A previous batch wrote a shortened contract id in an issue text and
five contributors invented plausible-looking ids to fill the gap. Write the
whole thing or do not write it at all.

The house pattern for an outbound deadline already exists — see
src/alerts/delivery.ts, which passes signal: AbortSignal.timeout(10_000) to
fetch. Where an issue below asks for a timeout, copy that, do not invent a
second convention.

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

主要言語
TypeScript
スター
4
フォーク
71
平均マージ
3日 14時間
マージ済み PR（30日）
157

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Divinity-Labs/Lens のほかの issue

Divinity-Labs/Lens の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。