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

Aperta
#2,735 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
node.js, python, rust
Ambito
api, backend, security

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Rust
Stelle
2
Fork
0
Merge medio
9h 48m
PR unite (30g)
151

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

Tutte le issue di registrystack/registry-stack

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.