Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#767 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
68/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
build-system, cli

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Rust
Estrelas
468
Forks
42
Merge médio
2d 31min
PRs com merge (30d)
46

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de voidzero-dev/vite-task

Todas as issues de voidzero-dev/vite-task

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.