Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Ingester loops have no upper bound on a single cycle

Abierto
  • ¿Algo no está bien?
#351 4 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@felixumeh ya está trabajando en esto.

Desde el 16/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

Each ingester is an infinite loop restarted on crash by restartIngester. There
is no limit on how long one iteration may take. With L162's missing timeouts, a
single slow upstream can stretch one cycle indefinitely; the loop has not
crashed, so nothing restarts it, and the venue goes quiet without any error
being raised anywhere.

This is the most dangerous shape in this batch, because every monitoring signal
the service currently has reports it as healthy.

What to build
  • A per-cycle deadline. A cycle exceeding it is abandoned and the next one
    starts, rather than waiting forever.
  • Count abandoned cycles in a metric, labelled by venue and network.
  • Make sure abandoning a cycle cannot leave a partial write committed — check
    how each ingester writes before changing the control flow.
  • Overlap must remain impossible: abandoning a cycle must not start a second
    concurrent one against the same venue.
Acceptance criteria
  • A cycle that exceeds its deadline is abandoned, not awaited indefinitely
  • The deadline is configurable per ingester
  • Abandoned cycles are counted in a metric
  • No partial write survives an abandoned cycle
  • A test with a slow upstream proves the loop keeps making progress

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

Lenguaje dominante
TypeScript
Estrellas
4
Forks
71
Merge medio
1 d 15 h
PR fusionados (30 d)
28

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Divinity-Labs/Lens

Todos los issues de Divinity-Labs/Lens

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.