coordinator: add scheduling.publish-windows/v1 so a workflow can turn a record into bookable windows
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
調査の方向性
Start with the operation catalogue in crates/registry-coordinator/src/operations.rs and the coordinator flow described in docs/site/src/content/docs/explanation/how-coordinator-works.mdx; the issue also depends on #2732. Trace how Scheduling operations are previewed and applied, then review the linked work for publishing windows. Done means the native journey covers create, update, withdrawal and replay, refusals surface their problem code, and operation schemas and contracts are regenerated.
索引モデルが issue の本文から書いたものです。
説明
Use case
The common composition is a registry record event, then a reviewed mapping, then published bookable windows. For example, a training session, exam sitting or public activity is recorded in BReg and becomes bookable. Adopters should be able to wire that with configuration and one mapping Function, not a bespoke service.
Current evidence
- Coordinator accepts the signed BReg record event and runs reviewed Functions. Its operation catalogue has Scheduling reads and booking operations, but no supply write.
- Coordinator has no dynamic fan-out. Publishing one snapshot per record event needs none.
Proposed behaviour
scheduling.publish-windows/v1, with preview and apply, calling #2732 under Coordinator's own Scheduling credential and the source profile the operator configured for it.- Idempotent by the source record's revision. One call per record event.
- An example project: BReg record event, then a Rhai mapping Function that turns the record into a window snapshot (including bounded expansion of recurring sessions), then
scheduling.publish-windows/v1.
Acceptance criteria
- In a native journey, creating, updating and withdrawing a BReg record publishes, replaces and withdraws its windows.
- Replay after a Coordinator restart publishes once.
- A Scheduling refusal surfaces as a Run failure with the product's problem code.
- Operation schemas and contracts are regenerated.
Delivery
Implemented in one PR with #2731 and #2732.
- 主要言語
- Rust
- スター
- 2
- フォーク
- 0
- 平均マージ
- 9時間 48分
- マージ済み PR(30日)
- 151
環境構築
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
registrystack/registry-stack のほかの issue
-
area:breg enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
registrystack/registry-stack#2765 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
registrystack/registry-stack#2761 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
registrystack/registry-stack#2743 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
registrystack/registry-stack#2706 ·
メンテナーはふだん 1 日以内に返信
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
registrystack/registry-stack#2704 ·
メンテナーはふだん 1 日以内に返信
registrystack/registry-stack の issue をすべて見る
似ている issue
-
help wanted needs investigation priority: low
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
tomast1337/Puppeter-PptxGenJS#440 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
n0-computer/iroh#4709 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 75/100
qingjian-team/qingjian#1114 ·
メンテナーはふだん 2 日以内に返信