☂️ Cache tools that maintain their own cache

Aperta
  • Qualcosa non va?
#929 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
5/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
build-system

Direzione di ricerca

This is a tracking epic for the read-write overlap work, not a single change, and the payload names no files or tests. Start with the linked pull requests in the listed merge order (#914 to #919), then the label query for read-write overlap PRs. Done means the Goal's behaviour holds and the Next and Related items are resolved, and the diagnostics design still needs a maintainer decision.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

read-write overlap

Part of the 2026 Q4 plan (P0).

Goal

Tools such as Vitest, TypeScript and Astro read and rewrite their own cache files, and many build tools read back the folders they write. vp run used to refuse to cache a task whose reads and writes overlap. Cache these tasks without manual exclusions in cache.input or cache.output, and make every hit and miss explainable, so a person or an AI agent can tell why a task missed and what would make it hit.

The remote cache depends on this. In trials on real workspaces, most tasks either couldn't be cached or missed on every fresh checkout.

Done

  • Cache tasks that rewrite files they read: #913
  • Restore output symlinks as links: #885, #911
  • pnpm's own files no longer break hits: #823, #824, #825, #850
  • Miss explanations: #783, #784
  • Earlier groundwork: #248 (skip caching tasks that modify their inputs), #431 and #459 (inputs and outputs that tools ask vp run to ignore)

In progress

Merge in this order:

  1. #914 Let a hit rebuild folders that hold only the task's outputs
  2. #915 Let a listed folder lack entries a hit can rebuild
  3. #916 Treat files and folders renamed into place as outputs (fixes #908)
  4. #917 Let a hit rebuild empty folders the task made
  5. #918 Restore symlinks a task creates
  6. #919 Stop skipping dist in directory listings

Diagnostics: with the new rules, people and AI agents need to see why a task missed more than before. Planned: --json output with the full file system fingerprints and every miss reason (#791, voidzero-dev/vite-plus#2848). The design isn't settled.

Next

  • #548 Windows reports the workspace root as a read-write overlap
  • #910 Files cp writes on macOS aren't recorded as outputs
  • #482 Tools disable caching too early (disableCache trigger points)
  • #905 An input edited while the task runs is fingerprinted after the run

Related pull requests from contributors

  • #869 Fingerprint only whether probed files exist (#860)
  • #794 Skip reads inside folders tagged with CACHEDIR.TAG (#793)
  • #903 Skip .git in directory listings, so a git worktree can replay a checkout's entries (#902). #919 changes the same skip list.
  • #792 vp run --dry-run, related to the diagnostics work

All pull requests: label:"read-write overlap"

Lingua principale
Rust
Stelle
485
Fork
51
Merge medio
23h 40m
PR unite (30g)
55

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di voidzero-dev/vite-task

Tutte le issue di voidzero-dev/vite-task

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.