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

A crash-looping ingester is invisible

未关闭
  • 哪里不对？
#331 2 条评论 0 个 reaction 已指派 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 小时
30 天内合并 PR
34

环境准备

从这里开始

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

Divinity-Labs/Lens 的其他 Issue

查看 Divinity-Labs/Lens 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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