casework: operator reads for review requests and completion deliveries, and redelivery of a dead-lettered completion

Abierto
#2,735 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
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
node.js, python, rust
Área
api, backend, security

Línea de trabajo

Start in crates/registry-casework/src/runtime/completion.rs to see how pending, retrying and dead-lettered deliveries are modelled, then find an existing operator route in another product and copy its list/detail/cursor shape. The review-request gauges are the only current read path, so locate where they are computed before adding a listing route. Done means the two reads and the redelivery action exist with idempotency, reason and audit, plus matching Rust, Node and Python client methods and tests for paging and the dead-letter transition.

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

Descripción

Casework counts its review requests in metrics, but nothing lists them. Its completion deliveries can only be seen in the database.

Today

  • The review-request gauges count requests by state. No route or command lists them by state or age.
  • Completion deliveries (pending, retrying, dead-lettered; crates/registry-casework/src/runtime/completion.rs) have no API or CLI. A dead-lettered completion has no way back short of database work.
  • Overdue work is a count, not a list. The supervision feed omits due dates and holders by design, so an operator list must keep that rule.

Ask

Read routes:

  • Review requests by state and age, without holders or content.
  • Completion deliveries by state, with attempts and the last failure class.

Action, after the reads:

  • Redeliver a dead-lettered completion.

Shape

These routes follow the same shape as the other products' operator routes. It is a convention, not a shared contract:

  • A list of held or failed work with state, age and cursor paging, plus a detail read.
  • Actions only after the reads ship. Each action takes one item at a time, with a reason and an idempotency key. The product's own access profile authorises it for a named person's token, and the audit records it under that person.
  • Maintained client methods (Rust, and the Node and Python facades) in the same change.
  • An operator disclosure profile. The routes return identifiers, states, ages and failure classes, not record content or personal data.
  • Security review notes in the pull request, because each route widens what an operator token can read or change.
Lenguaje dominante
Rust
Estrellas
2
Forks
0
Merge medio
9 h 48 min
PR fusionados (30 d)
151

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 registrystack/registry-stack

Todos los issues de registrystack/registry-stack

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.