☂️ Cache tools that maintain their own cache

オープン
  • 何か問題がありますか？
#929 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
5/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
rust
領域
build-system

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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"

主要言語
Rust
スター
485
フォーク
51
平均マージ
23時間 40分
マージ済み PR（30日）
55

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

voidzero-dev/vite-task のほかの issue

voidzero-dev/vite-task の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。