scheduling: operator reads and actions for dead-lettered outbox work and hook deliveries
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
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 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.
- Linguagem predominante
- Rust
- Estrelas
- 2
- Forks
- 0
- Merge médio
- 9h 48min
- PRs com merge (30d)
- 151
Preparar o ambiente
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de registrystack/registry-stack
-
area:breg enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
registrystack/registry-stack#2765 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
registrystack/registry-stack#2761 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
registrystack/registry-stack#2743 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
registrystack/registry-stack#2706 ·
Mantenedores costumam responder em até 1 dia
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
registrystack/registry-stack#2704 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de registrystack/registry-stack
Issues semelhantes
-
help wanted needs investigation priority: low
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
-
[Bug] 建议把黑白主题设置同步到启动页面Abertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
tomast1337/Puppeter-PptxGenJS#440 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
n0-computer/iroh#4709 ·
Mantenedores costumam responder em até 1 dia
-
生词本里,已标记为认识的词,按钮写「不认识了」读着别扭Aberta
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 75/100
qingjian-team/qingjian#1114 ·
Mantenedores costumam responder em até 2 dias