☂️ Cache tools that maintain their own cache

Ouverte
  • Quelque chose ne va pas ?
#929 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
5/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
rust
Domaine
build-system

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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. RFC: #933 (vp run --dry-run with every miss reason, and vp run --json for the task graph; #791, voidzero-dev/vite-plus#2848).

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"

Langage dominant
Rust
Étoiles
485
Forks
51
Merge moyen
23 h 20 min
PR mergées (30 j)
56

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de voidzero-dev/vite-task

Toutes les issues de voidzero-dev/vite-task

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.