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

/status does not say whether ingestion is actually working

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

Los mantenedores suelen responder en 1 día

@Oluoma123 ya está trabajando en esto.

Desde el 16/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

/status is defined at src/api/rest.ts:72 and is the endpoint an uptime
monitor will poll. It answers from the process's own point of view. It does not
report whether any ingester is running, when each venue last produced a price,
or whether an ingester has been crash-looping — which means a service with every
ingester dead still returns a healthy /status and a green uptime check.

This is the issue that makes L163 and L165 useful: both produce information that
currently has nowhere to go.

What to build

Extend /status with per-venue, per-network ingestion health:

  • Last successful write time per (venue, network), and the age of it.
  • Whether that age exceeds an expected interval for that venue.
  • Restart count and last crash message, if L165 has landed; design for it being absent.
  • An overall verdict that an uptime monitor can alert on.

Keep the existing fields — callers depend on them. The route is public: true
and allow-listed from rate limiting in src/app.ts, so it must stay cheap: no
unbounded queries, and do not add a Horizon round-trip to it.

Acceptance criteria
  • /status reports last-write age per venue and network
  • A stale venue is visibly distinct from a healthy one
  • Existing response fields are unchanged
  • The handler issues a bounded, small number of queries regardless of how many pairs exist
  • A test asserts the stale case is reported as unhealthy

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.