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

Hints: webhook deliveries mode

Abierto
  • ¿Algo no está bien?
#37 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
github, typescript, yaml
Área
api, backend, web-dev

Línea de trabajo

Read ADR 0014 and the referenced CONTEXT.md and ADRs 0001–0019 first; inspect the implementation for polling triggers (#28), board drag and label sync (#33), the existing HTTP server, and runtime store. Define the hint seam and delivery modes against those dependencies, then check each acceptance criterion, including deduplication, cursor persistence, webhook verification, UI status, and the unchanged 60s poll.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

agent-in-progress

Parent

Implementation breakdown of the build-ready spec — map #1; spec = CONTEXT.md + ADRs 0001–0019.

What to build

Latency without touching correctness: a Hint nudges the engine to fetch a repo's or item's state sooner than the next poll. Self-write hints make the board drag feel instant; the two webhook modes bring sub-poll latency for outside changes — all behind one seam, with polling remaining the sole correctness source and the dedup ledger the sole event gate.

Spec: ADR 0014.

Acceptance criteria

  • The hint seam: a droppable (repo, optional item) nudge that only schedules the existing change-detection / slice fetch earlier — never a new event path; a dropped hint costs freshness only, a doubled hint dedups to nothing; the 60s backstop poll runs unchanged
  • Self-write hints always on: after any usine write to GitHub (board-drag label swap, ask comment), the engine hints itself — a board drag reflects in about a second
  • webhooks.mode in usine.yaml, default off
  • deliveries mode: JWT-polls the App's webhook-delivery log on an engine-fixed ~10s cadence, routing repo-level hints from summary fields without payload fetches; cursor persists in the runtime store; ping and unregistered repos ignored
  • endpoint mode: serves an HMAC-SHA256-verified webhook route on the orchestrator's existing HTTP server, taking item-level hints from payloads; webhooks.public_url required; usine PATCHes the App's hook URL on every mode/config change
  • UI: Configuration shows the mode and last-hint-received; the needs-you strip warns when endpoint mode has never received a delivery — display + warn only, engine behavior never consults hint health

Blocked by

  • #28 — Polling triggers: change detection to content-hashed Events
  • #33 — Board: lanes, two-way label sync, drag as a trigger surface

Decisions (2026-10-28)

Self-write hints are built (packages/orchestrator/src/polling/hints.ts, ADR 0014), and the webhooks schema exists (packages/config/src/factory.ts). This issue now covers the deliveries mode only; the endpoint mode is #679.

  • Extend ItemHints with a repository-level hint (item optional) that runs that repository's change detection early. Keep the dropping queue of 128.
  • deliveries mode: poll GET /app/hook/deliveries with the App JWT about every 10 seconds. Persist the cursor beside CursorStore, ignore ping and unregistered repositories, and fetch no payloads.
  • webhooks stays a setting read at startup (current-instance/changes.ts).
  • Settings shows the mode and the last hint time.
  • Tests with a scripted deliveries API: a delivery for a registered repository hints its change detection once; ping and unknown repositories are ignored; the cursor survives a restart.
Lenguaje dominante
TypeScript
Estrellas
1
Forks
0
Merge medio
4 h 39 min
PR fusionados (30 d)
243

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 basaltbytes/usine

Todos los issues de basaltbytes/usine

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.