Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Preserve and recover cloud workspace files beyond the pilot checkpoint limit

Abierto
  • ¿Algo no está bien?
#413 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
git, typescript
Área
backend, cloud

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
1
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/ace2

Todos los issues de githubnext/ace2

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.