Establish authoritative SessionGroup membership and session catalog lifecycle
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 20/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- go
調査の方向性
Start by reviewing the linked contracts in #2761, #2760, #2665, #2669, #2670, #2671 and #2672, then trace the existing Go session and history creation, publication, lookup and activation paths. Define the catalog authority, persistence and failure model before implementing; the issue requires review before implementation and deterministic tests at the storage and activation boundaries. Done means membership, publication and tombstones remain authoritative across interruptions, deletion, restart and owner changes, with delegation behavior qualified against #2671.
索引モデルが issue の本文から書いたものです。
説明
Outcome
An authoritative catalog records SessionGroup identity, permanent Session/history membership, session existence/publication, and logical deletion independently of whether history bytes already exist. Deletion and retained references cannot re-enable execution/access or permit identity reuse.
Parent: #2666, under #2659. This carries catalog and lifecycle obligations moved out of #2761's bounded group-lease contract and two-history memory proof. #2761 supplies ownership/fencing primitives, not catalog authority.
Scope
- Define and implement authoritative group/session creation, member registration, publication, lookup and logical deletion. A group may be empty and has no intrinsically distinguished root member.
- Assign each Session/history permanently to one group. Register new members under the correct group authority; do not implement cross-group migration. Distinguish membership from initialized history, loaded runtimes, principal authorization and execution authority.
- Review the catalog/manifest persistence and creation/publication ordering contract, including interruptions before any accepted history exists. A backend index or routing table is not a competing catalog.
- Specify deletion tombstones/identity retirement, activation/access checks and cleanup without claiming immediate physical purge. Session and group identities are not reused or silently reassigned.
- Coordinate delegation lifecycle policy with #2671: where a parent/root deletion must disable owned delegated work, enforce that policy consistently without assuming every group member is a child or that deleting any member deletes its peers. Retained history/environment references cannot resurrect disabled or expired resources.
Acceptance
- Catalog and membership authority, storage schema, failure model, access/execution boundaries and Go/stored/wire compatibility are reviewed before implementation.
- Creation/member publication interrupted before, during and after first-history acceptance produces explicit reconcilable states, without duplicate identity or an independently activatable orphan.
- Concurrent registration/activation and stale-owner operations cannot assign a member to two groups, bypass the group lease or reinterpret absent history as absent membership.
- Logical deletion prevents prohibited activation/access and ID reuse even before history creation, after runtime eviction, and after restart or owner change; cleanup is distinct from deletion authority.
- Delegation deletion/cancellation integration is qualified with #2671, including stale child advancement and direct API Team creation where applicable. SessionGroup itself has no required root.
- Deterministic tests exercise actual catalog/storage and activation boundaries with isolated state, plus bounded handling of corruption/uncertainty. Residual deployment qualification is explicitly assigned.
Dependencies and boundaries
Coordinate #2761 leases/fencing, #2760 durable history, #2665 interrupted recovery, #2669 shared controls, #2670 authorization/provenance, #2671 delegation and #2672 final cutover qualification. Reuse accepted history identities without importing the legacy Session aggregate or treating diagnostic InstanceID as authority.
No automatic cross-owner private-output replay, cross-group migration, implicit cross-history transaction, production cutover, physical purge promise or schema/API break is authorized by filing this issue. Preserve the existing separation between principal access and execution leasing.
- 主要言語
- Go
- スター
- 309
- フォーク
- 29
- 平均マージ
- 15時間 56分
- マージ済み PR(30日)
- 225
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
stacklok/mecatl のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
docs: make local provider configuration discoverable from mecatui再び着手できるかも @brainsparker が 28 日前に担当しましたが、オープン中のプルリクエストはありません。 オープンdocumentation
難易度 2/5 1〜3時間 初心者へのやさしさ 73/100
stacklok/mecatl#2470 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
メンテナーはふだん 1 日以内に返信
-
Flake: MCP handshake cancellation can outlive authorization send deadline対応中かも @jbeda が今日担当しました。 オープン
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
メンテナーはふだん 1 日以内に返信
stacklok/mecatl の issue をすべて見る
似ている issue
-
HTTP probe loses insecureSkipVerify in the generated probe manifest対応中かも @BahaaMattar が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 87/100
litmuschaos/litmus#5745 ·
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
メンテナーはふだん 2 日以内に返信
-
type/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
メンテナーはふだん 1 日以内に返信
-
messaging/v1: IsGRPCProtocol and InternalMetadataToGrpcMetadata panic on empty or nil metadata values対応中かも @patelshivani2283-lab が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
メンテナーはふだん 1 日以内に返信
-
needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
stacklok/toolhive-catalog#2024 ·
メンテナーはふだん 1 日以内に返信