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

A cache hit whose outputs can't be restored exits 0 and is reported as a hit

Abierto
  • ¿Algo no está bien?
#767 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
build-system, cli

Línea de trabajo

Reproduce the failure with vp run build after deleting the task archive under node_modules/.vite/task-cache/, then inspect the cache-hit restoration and task-summary paths used by vp run --last-details. Done means a failed restore produces a non-zero exit, is shown as a task failure rather than a cache hit, and does not leave the broken cache entry for later runs.

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

Descripción

remote cache

When vp run gets a cache hit but can't restore the task's output files, for example because the cached archive was deleted or is corrupt, it prints an error, but:

  • the run exits with code 0, so CI passes without the task's outputs;
  • the summary line still says cache hit;
  • vp run --last-details shows the task with ✓ as a cache hit, without the error.

The broken entry also stays in the cache, so every later run hits it and fails the same way until vp cache clean.

Remote caching makes this easier to reach. An entry from the remote cache is saved locally before its outputs are restored, so an archive that downloads but can't be restored leaves the same broken entry behind (#756).

Steps to reproduce

  1. Run a cached task that has output files, such as vp run build.
  2. Delete its .tar.zst archive under node_modules/.vite/task-cache/.
  3. Run vp run build again and check the exit code, then run vp run --last-details.
$ … ◉ cache hit, replaying
✗ Cache lookup failed: failed to restore cached outputs from …/node_modules/.vite/task-cache/v18/….tar.zst; the archive may have been deleted or corrupted. Run `vp cache clean` to clear the cache.: No such file or directory (os error 2)

---
vp run: cache hit, 94ms saved.

The exit code is 0, and --last-details shows:

Statistics:   1 tasks • 1 cache hits • 0 cache misses
...
  [1] my-package#build: $ … ✓
      → Cache hit - output replayed - 94ms saved

Expected: the run fails with a non-zero exit code, the summary reports the task as failed with its error, and later runs don't keep hitting the broken entry.

Lenguaje dominante
Rust
Estrellas
468
Forks
42
Merge medio
1 d 10 h
PR fusionados (30 d)
43

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 voidzero-dev/vite-task

Todos los issues de voidzero-dev/vite-task

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.