Preserve and recover cloud workspace files beyond the pilot checkpoint limit
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 12/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- git, typescript
調査の方向性
Start in the services/compute pilot, reading the compute Durable Object's checkpoint code and its explicit lifecycle calls, including the 16 MiB limit and single retained generation. Measure full versus incremental capture of a real repository (transfer size and restore time) before choosing an approach. Done means a manifest is published only after complete data, a restore after container loss or resize brings back the staged, untracked, and ignored files with Git state intact, and an interrupted capture keeps the previous generation.
索引モデルが issue の本文から書いたものです。
説明
Follow-up to #216 and the services/compute pilot.
The pilot keeps a full gzip/tar checkpoint in its compute Durable Object, limited to 16 MiB and one retained generation. Checkpoints happen through explicit lifecycle calls. A lost container can recover the last complete checkpoint, but work after that checkpoint can be lost. This is enough to test the workspace boundary; it does not provide the recovery guarantees needed for routine remote development.
Extend filesystem checkpointing and recovery while keeping channel messages, runs, and chats exclusively in pi. R2-backed snapshots and incremental file/block storage are candidates to measure, not features the pilot already implements. Start by comparing full and incremental captures on real repositories, including their transfer size and restoration time, then choose the simplest approach that meets the recovery window and storage limits.
Acceptance:
- Preserve the full repository state:
.git, refs, worktree metadata and absolute paths, staged and unstaged edits, untracked files, and ignored files. Keep dependency/cache exclusions explicit and reproduce required dependencies before work resumes; Git push alone is not a workspace backup. - Publish a checkpoint manifest only after its data is complete. Verify integrity before restoration, retain the previous valid generation on capture failure, and bound retention and cleanup of abandoned generations.
- Define when checkpoints occur and the maximum expected recovery window. Expose the latest successful generation and capture failures so partial durability is not presented as every write being saved.
- Quiesce filesystem writers before capture. Process memory and running daemons remain outside the checkpoint contract; document the stop/restart requirements instead of implying those processes survive restoration.
- Restore a complete workspace at the recorded paths before allowing channel tools to resume. Missing or corrupt checkpoint data must preserve the recovery evidence and refuse an empty replacement.
- Exercise real recovery after container loss and resizing with a dirty lane, staged changes, an untracked file, an ignored file, and an interrupted capture. Verify Git/worktree state and the restored file contents, as well as the reported recovery point.
Scope is filesystem durability and recovery. Desktop discovery, agent sizing decisions, and a second channel-history store are outside this issue.
- 主要言語
- TypeScript
- スター
- 1
- フォーク
- 0
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
githubnext/ace2 のほかの issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 94/100
githubnext/ace2#487 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 90/100
githubnext/ace2#486 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
githubnext/ace2#459 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
githubnext/ace2#437 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
githubnext/ace2#442 ·
githubnext/ace2 の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
paperclipai/paperclip#16785 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
code-yeongyu/senpi#3661 ·
メンテナーはふだん 1 日以内に返信
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
難易度 1/5 1時間未満 初心者へのやさしさ 78/100
lingdojo/kana-dojo#32731 · コメント 1 件 · リアクション 5 件 ·
メンテナーはふだん 1 日以内に返信
-
bug status: needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
mastra-ai/mastra#27538 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
Yeachan-Heo/oh-my-codex#3822 ·
メンテナーはふだん 1 日以内に返信