breg: operator HTTP reads and actions for import runs, blocked Proposal applications and hook dead letters
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
- 12/100
Direção de pesquisa
Start by reading crates/registry-breg/src/api/ingestion.rs and crates/registry-breg/src/ingestion_store.rs to see how import runs are currently scoped to their creator, then find an existing product's operator routes to copy the list/detail shape from. Map the three read routes (import runs, blocked Proposal applications, dead-lettered hook deliveries) before touching the actions, since actions depend on the reads. Done means list and detail routes with state, age and cursor paging, action routes with reason and idempotency key, maintained Rust/Node/Python client methods, and disclosure-profile plus security notes in the pull request.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Operators can find stuck BReg work only through bregctl on the host, and some of it not at all.
Today
- Import runs can be read only by their creator (
crates/registry-breg/src/api/ingestion.rs,crates/registry-breg/src/ingestion_store.rs). No operator-wide list or detail exists. - Blocked Proposal applications are a gauge (
breg_proposal_application_blocked_jobs), not a list. - Hook dead letters are visible only through the CLI, and the list can fail or omit rows (#1798, #1796).
- There is no HTTP route for any hook, timer or retention action, and CLI actions carry no named person.
Ask
Read routes:
- Import runs across creators, by state, with a detail read.
- Blocked Proposal applications, with the failure class and age.
- Outbound hook deliveries by state, including dead-lettered.
Actions, after the reads:
- Retry or discard a dead-lettered hook delivery.
- Requeue a blocked Proposal application.
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.
Related: #1492 (import run management), #1432, #2096, #1798, #1796.
- 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