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

Nothing proves a deployed instance can actually answer

Cerrado
  • ¿Algo no está bien?
#346 2 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 2 días

@krsnak ya está trabajando en esto.

Desde el 16/10/2026.

  • #355 de @krsnak — abierto
  • #481 de @sparkysolutions10-pixel — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

CI runs unit tests against mocks. Nothing checks that a running Lens answers
correctly — that /price returns a number with the right shape, that /status
is healthy, that the websocket accepts a subscription and pushes an update.

The failures in this batch are precisely the ones unit tests cannot catch: a
hung fetch, a dead ingester, an exhausted pool. All of them leave the process up
and the tests green.

What to build

A smoke check that runs against a URL and exits non-zero on failure:

  • /status and /ready report healthy.
  • /price for a known pair returns a well-formed response within a time budget.
  • The websocket accepts a connection, takes a subscription and delivers at least
    one message, or times out.
  • Prices are fresher than a threshold, not merely present.

It must take the base URL as an argument so it works against local, staging and
production, and it must not require credentials beyond what a normal caller has.

Acceptance criteria
  • A single command runs the smoke check against any base URL
  • It exits non-zero on any failure and prints which check failed
  • It asserts freshness, not just presence
  • It covers at least one websocket round-trip
  • It runs in well under a minute and is documented in the README

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
2 d 20 h
PR fusionados (30 d)
127

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.