Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

There is no readiness check, only a status page

Chiusa
  • Qualcosa non va?
#334 3 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

@CollinsKRO ci sta già lavorando.

Dal 16/10/2026.

  • #467 di @sparkysolutions10-pixel — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

area:reliability difficulty:easy help wanted points:100 Stellar Wave
Background

/status is the only health-ish endpoint. A platform needs two different
answers and they are not the same question:

  • liveness — is this process wedged and in need of a kill? Must not depend on
    Postgres or Redis, or a database blip restarts healthy processes in a loop.
  • readiness — should this process receive traffic yet? Must check that
    migrations are applied and dependencies are reachable, so a starting instance
    is not sent requests it will fail.

Lens starts ingesters, a Redis-backed retention worker and a websocket fanout
before it is genuinely able to serve, so the gap is real.

What to build
  • /live — no dependency checks, returns healthy if the event loop is turning.
  • /ready — checks Postgres and, where configured, Redis; returns unhealthy
    until the app has finished booting.
  • Both public: true and allow-listed from rate limiting, as /status is.
  • Neither should be expensive enough to matter when polled every few seconds.
Acceptance criteria
  • /live returns healthy without touching Postgres or Redis
  • /ready returns unhealthy before boot completes and healthy after
  • /ready reports unhealthy when Postgres is unreachable
  • Both are excluded from rate limiting and from httpMetrics route cardinality
  • /status is unchanged

Drips Wave · Complexity: Easy · 100 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

Lingua principale
TypeScript
Stelle
4
Fork
71
Merge medio
3g 6h
PR unite (30g)
144

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Divinity-Labs/Lens

Tutte le issue di Divinity-Labs/Lens

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.