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

オープン
#2,735 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
18/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
node.js, python, rust
領域
api, backend, security

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
Rust
スター
2
フォーク
0
平均マージ
9時間 48分
マージ済み PR(30日)
151

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

registrystack/registry-stack のほかの issue

registrystack/registry-stack の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。