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

A crash-looping ingester is invisible

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

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

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

2026年10月16日 から。

  • #467 @sparkysolutions10-pixel による — オープン
  • #479 @Notdayo による — オープン

評価

この issue はまだ評価されていません。

説明

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

src/index.ts restarts a crashed ingester like this:

const restartIngester = (name: string, network: NetworkName, fn: () => Promise<void>) => {
  fn().catch(err => {
    console.error(`[lens] ${name}/${network} ingester crashed, restarting in 10s:`, err.message)
    setTimeout(() => restartIngester(name, network, fn), 10_000)
  })
}

The fault isolation is good and the comment above it explains the design well.
What is missing is any awareness of how often this happens. An ingester that
crashes immediately on start will restart every ten seconds forever. There is no
backoff, no cap, no metric, and /status does not mention it — so the service
reports itself healthy while one venue has produced nothing for a week.

What to build
  • Exponential backoff with a ceiling, instead of a flat ten seconds.
  • A counter metric of restarts, labelled by ingester name and network, exported
    through the existing prom-client registry in src/metrics.ts.
  • A record of the last crash — time and message — per (ingester, network), so
    L167 can surface it on /status.
  • Reset the backoff once an ingester has run healthily for some period, so a
    nightly blip does not permanently slow restarts.
Acceptance criteria
  • Restart delay grows on repeated failure and is capped
  • Backoff resets after a sustained healthy run
  • A Prometheus counter exposes restarts per ingester and network
  • Last crash time and message are retrievable per ingester
  • The existing fault isolation is preserved — one venue crashing still cannot affect another

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
平均マージ
1日 9時間
マージ済み PR（30日）
34

環境構築

はじめの一歩

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

Divinity-Labs/Lens のほかの issue

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

似ている issue

TypeScript の issue をもっと見る

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

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