scheduling: operator reads and actions for dead-lettered outbox work and hook deliveries

Aberta
#2,737 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
22/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
nodejs, python, rust

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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 intents lists, 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.
Linguagem predominante
Rust
Estrelas
2
Forks
0
Merge médio
9h 48min
PRs com merge (30d)
151

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de registrystack/registry-stack

Todas as issues de registrystack/registry-stack

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.