Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Preserve and recover cloud workspace files beyond the pilot checkpoint limit

Offen
  • Stimmt etwas nicht?
#413 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
12/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
git, typescript
Bereich
backend, cloud

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
0
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/ace2

Alle Issues in githubnext/ace2

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.