scheduling: operator reads and actions for dead-lettered outbox work and hook deliveries
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
- 22/100
Línea de trabajo
Start from crates/registry-scheduling/src/hooks.rs, where hook deliveries are captured with operator_replay: false, then inspect the Scheduling outbox schema and how schedulingctl intents lists items. Compare the existing operator routes in other products for the list/detail/action shape before adding the outbox and hook-delivery reads. Done means both read routes with state, age and cursor paging; one-item actions with reason and idempotency key; audit under the named operator; and Rust/Node/Python client methods.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Dead-lettered and expired Scheduling outbox work can be seen only in the database. Nothing can retry or discard it.
Today
- Reminders, observer-hook delivery and retention run as outbox work. Dead-lettered and expired outbox rows, and dead-lettered hook deliveries, have no route or command.
- Hook deliveries are captured with
operator_replay: false(crates/registry-scheduling/src/hooks.rs). Replay is off by design today, so this issue needs a decision on whether operator replay is allowed. schedulingctl intentslists, but cannot act.
Ask
Read routes:
- Outbox work by kind and state, including dead-lettered and expired.
- Observer-hook deliveries by state.
Actions, after the reads:
- Requeue or discard a dead-lettered outbox item.
- Replay a dead-lettered hook delivery, if replay is allowed.
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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de registrystack/registry-stack
-
area:breg enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
registrystack/registry-stack#2765 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
registrystack/registry-stack#2761 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
registrystack/registry-stack#2743 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
registrystack/registry-stack#2706 ·
Los mantenedores suelen responder en 1 día
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
registrystack/registry-stack#2704 ·
Los mantenedores suelen responder en 1 día
Todos los issues de registrystack/registry-stack
Issues similares
-
[Bug] 建议把黑白主题设置同步到启动页面Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
stackabletech/airflow-operator#898 ·
Los mantenedores suelen responder en 1 día
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)Posiblemente ocupada @zyl71 la tomó hoy. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100