Repository navigation
feat(cache): let a listed folder lack entries a hit can rebuild - #915
Merged
wan9chi merged 2 commits intoNov 5, 2026
Merged
Conversation
wan9chi
force-pushed
the
feat/cache-listing-ignored-entries
branch
from
October 30, 2026 03:19
7f01a6e to
531c594
Compare
fspy benchmarklinuxmacoswindows |
wan9chi
force-pushed
the
feat/cache-listing-ignored-entries
branch
from
October 30, 2026 04:07
531c594 to
524114b
Compare
wan9chi
force-pushed
the
feat/cache-listing-ignored-entries
branch
from
October 30, 2026 06:31
524114b to
f92e4fd
Compare
wan9chi
force-pushed
the
feat/cache-listing-ignored-entries
branch
from
October 30, 2026 07:08
f92e4fd to
912534a
Compare
wan9chi
force-pushed
the
feat/cache-listing-ignored-entries
branch
from
November 5, 2026 08:54
912534a to
2181f79
Compare
…akes it miss Two cases for a task that lists a folder holding its own output folder. In `list_folder_holding_output`, the task makes `gen`, writes `gen/a.txt` and lists the package root, through `vtt fs`. In `typescript_lib_out_dir`, TypeScript 7's `tsc` with no `include` compiles `src` into `lib`: it lists the package root and stats `lib`. Today removing the output folder, as on a clean checkout, is a cache miss naming the folder as removed from the listing, although the cached outputs hold everything in it. A new entry in the listing is a miss too, and must stay one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A task that lists a folder holding its own outputs, like TypeScript 7's `tsc` with no `include` listing the package root that holds its `lib` output folder, pinned those outputs as entries of the listing. Removing them, as on a clean checkout, was a cache miss although the task writes them again. When a listing is fingerprinted, the entries the task can rebuild, a file or symlink it wrote or a folder holding only what it can rebuild, are now left out, and their names are recorded as the listing's `ignored_entries`. A listed folder's fingerprint is now a `DirListing` holding its entries and those names, so only a listing can carry them. Validation removes the same names from the current listing before comparing, so they may be missing or present, while any other entry that differs still misses and is named in the message. A hit restores them if they're among the task's outputs. `Rebuildable` answers whether an entry is rebuildable from the written paths and the folders its walk already found, so no folder is listed again, and a task that wrote nothing skips the check. `.DS_Store` and `dist` stay skipped in every listing and are never recorded. On a file system that doesn't report entry types, a Unix listing now stats each entry without following symlinks, as std does, instead of taking every entry for a file, so it tells folders apart the same way as `Rebuildable`'s walk. The cache schema version is bumped for the new listing format. `typescript_incremental` now runs on Windows too, where `tsc` also lists the package root, which holds the `tsconfig.tsbuildinfo` it wrote. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wan9chi
force-pushed
the
feat/cache-listing-ignored-entries
branch
from
November 5, 2026 09:02
2181f79 to
c7a32cb
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit c7a32cb. Configure here.
wan9chi
added a commit
that referenced
this pull request
Nov 5, 2026
…gs (#941) ## Motivation An exclusion in a task's `input`, like `"!build/**"`, leaves out only the paths the task reads. When the task lists a folder, every entry still counts, so an excluded folder appearing there is a cache miss: a lint task listing the package root misses once another task's build output appears in it. That is the case the hard-coded `dist` skip was added for (#181). #919 removes the skip, so users need a setting to get it back, and today `"!dist/**"`, which `docs/inputs.md` recommends, doesn't help. ## Changes Listings leave out what the input config excludes, after the entries the task can rebuild (#915): - An entry whose path the input negative globs match. A folder entry is matched by its own path; wax's `**` matches zero or more components, so `build/**` leaves out `build`, while `build/*` keeps it. The globs are part of the cache key, so validation applies the same ones to the current listing, and an entry that appears after the run is left out too. - An entry that a tool-reported `ignoreInput` path names. Those paths are known only after the run, so the names are recorded in the listing's `ignored_entries`, including entries that aren't there yet. The cache schema version is bumped. `docs/inputs.md` now says negatives also keep entries out of listings. E2E cases: `negative_glob_hides_listing_entry` (synthetic, `vtt list-dir` with `"!out/**"`; an unrelated new file still misses) and `oxlint_negative_build` (`oxlint -D no-debugger` with a gitignored `build/` and `"!build/**"`). Both miss today and hit after. A unit test covers `ignoreInput`. Part of a stack that lets automatic tracking cache tasks which read their own outputs and list the folders holding them, so they also hit on a clean checkout. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Changes post-run fingerprint semantics and cache validation for any task that lists directories with input negatives or ignoreInput; incorrect glob matching could cause stale cache hits, mitigated by schema bump and targeted tests. > > **Overview** > **Input exclusions now apply to directory listings**, not only to paths the task reads. Tasks that list a folder (e.g. a linter scanning the package root) no longer miss the cache when an excluded entry appears—such as another task’s `build/` folder after `"!build/**"`—as long as nothing else in the listing changed. > > Post-run fingerprints **omit listing entries** matched by the task’s input negative globs (same rules as reads: `build/**` drops the `build` folder entry; `build/*` does not) and by tool **`ignoreInput`** paths (names recorded in `ignored_entries` for validation). Cache hits recompile those globs from the entry key and apply the same filters when comparing listings. > > **Cache schema version is bumped to v22** (fresh cache). Docs and changelog describe the behavior; e2e covers `!out/**` with `list-dir` and an oxlint + `!build/**` scenario, plus a unit test for globs and `ignoreInput`. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 0655edb. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
wan9chi
added a commit
that referenced
this pull request
Nov 5, 2026
## Motivation Every directory listing skips an entry named `dist`. #181 added the skip so that a lint task listing the package root stays a cache hit when another task's build creates `dist` there. It helps no other folder name and hides a `dist` that does matter. A `dist` folder appearing in a folder the task listed goes unseen, and the next run replays stale output: `oxlint`, for example, passes from the cache after a `dist` folder with lint errors appears. ## Changes Listings skip only `.`, `..` and `.DS_Store`. A task that should ignore another task's `dist` gets that back with `"!dist/**"` in its `input`, which keeps the entry out of its listings since #941. A task's own `dist` doesn't need the skip, since #915 makes a rebuildable folder an ignored entry. The cache schema version is bumped, so entries recorded with the skip aren't reused. No other snapshot changes. E2E cases: `dist_appears_in_listed_folder` (synthetic, `vtt list-dir`) and `oxlint_dist` (`oxlint -D no-debugger`, with oxlint's rule count redacted). Both are false hits today and correct misses after. Part of a stack that lets automatic tracking cache tasks which read their own outputs and list the folders holding them, so they also hit on a clean checkout. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Medium Risk** > Changes cache fingerprint semantics for any task that lists directories, which can increase cache misses but fixes incorrect hits; schema bump invalidates existing local cache entries for the new version directory. > > **Overview** > Directory listings for cache fingerprints **no longer always omit a `dist` entry**. Only `.`, `..`, and `.DS_Store` are skipped when fingerprinting folder contents, so a **`dist` folder appearing or disappearing** in a listed directory now triggers a **cache miss** instead of replaying stale results (e.g. **oxlint** passing after bad code lands in a committed `dist/`). > > To keep ignoring another task’s **`dist`**, tasks can use **`"!dist/**"`** in **`input`** (listing exclusions from #941). A task’s **own** output **`dist`** still doesn’t affect listings when it only holds rebuildable outputs (#915). **`CACHE_SCHEMA_VERSION`** is bumped **22 → 23** so old fingerprints aren’t reused. > > E2E coverage adds **`dist_appears_in_listed_folder`** and **`oxlint_dist`** snapshots for the new miss behavior. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 625af30. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
fengmk2
added a commit
to voidzero-dev/vite-plus
that referenced
this pull request
Nov 11, 2026
Vite+ 1.6.0 caches `vp run` tasks that rewrite files they read, previews runs with `vp run --dry-run` and JSON output, lets `vp check --continue-on-error` report every failed check, and sets `VP_USER_AGENT` for the tools that `vp` starts. ### Features - `vp run` caches tasks that read files they also write, such as `tsdown --exports` rewriting `package.json` or `tsc --incremental` reading and writing `tsconfig.tsbuildinfo`. The files a task writes, and folders that hold only those files, may be missing on the next run, as on a fresh clone, and a cache hit restores them with the task's outputs, including the symbolic links the task created ([docs](https://viteplus.dev/guide/automatic-data-tracking#rebuildable-inputs)) ([vite-task#913](voidzero-dev/vite-task#913), [vite-task#914](voidzero-dev/vite-task#914), [vite-task#915](voidzero-dev/vite-task#915), [vite-task#916](voidzero-dev/vite-task#916), [vite-task#917](voidzero-dev/vite-task#917), [vite-task#918](voidzero-dev/vite-task#918)), by @wan9chi. - `vp run --dry-run` shows each command that a run would start and whether it would hit the cache, without running anything or writing to the cache. `vp run --json` prints every package and task in the workspace, and `vp run --dry-run --json` prints the run plan with each step's cache status, as one JSON document for scripts, CI, and coding agents. `vp run -v` lists every change behind a cache miss, including each changed input file, and `-vv` also lists the unchanged inputs and the outputs that a hit restores ([docs](https://viteplus.dev/guide/run#dry-runs-and-json-output)) ([vite-task#948](voidzero-dev/vite-task#948), [vite-task#960](voidzero-dev/vite-task#960), [vite-task#961](voidzero-dev/vite-task#961), [vite-task#963](voidzero-dev/vite-task#963), [vite-task#966](voidzero-dev/vite-task#966), [vite-task#967](voidzero-dev/vite-task#967), [vite-task#968](voidzero-dev/vite-task#968), [vite-task#969](voidzero-dev/vite-task#969)), by @wan9chi. - `vp check --continue-on-error` runs the remaining enabled checks after a failure, so one run reports formatting, lint, and type errors together, and exits with the status of the first failed check. Without the flag, `vp check` still stops at the first failed check ([#3367](#3367)), by @chbaefront. - `vp`, `vpr`, and `vpx` set `VP_USER_AGENT=vp/<version>` for their child processes, so tools can detect that Vite+ started them. When the global CLI delegates to a project's local CLI, the local version is reported ([docs](https://viteplus.dev/guide/global-cli#vp-user-agent)) ([#1958](#1958)), by @fengmk2. - First part of `VP_ENV_FORBIDDEN=1`, for systems such as NixOS that provide Node.js and package managers themselves: with it set, Vite+ never downloads a Node.js or package-manager version, shims and `vpx` use only the system tools on `PATH`, and installers and `vp upgrade` use the system `node` and `pnpm` for Vite+'s own dependencies. In this release, commands that delegate to a package manager, such as `vp install` and `vp run`, fail with `DisabledByEnvForbidden` while it is set. A follow-up change is planned to cover them and document the variable ([#3233](#3233)), by @myuron. - Upgrade the bundled Oxfmt and Oxlint ([#3416](#3416)), by @voidzero-guard[bot]: - `oxfmt@0.76.0` to `oxfmt@0.78.0`. Oxfmt formats Vue files with its own formatter instead of Prettier, so the output for Vue templates can change. It also fixes Tailwind class sorting in several layouts, Less escapes and `%` selectors, and TypeScript in Astro files. - `oxlint@1.91.0` to `oxlint@1.93.0` and `oxlint-tsgolint@7.0.2005` to `oxlint-tsgolint@7.0.2006`. `no-redeclare` gets an `ignoreDeclarationMerge` option, and `promise/prefer-catch` offers a suggestion. - Oxlint and Oxfmt resolve an unset or relative `root` in `vite.config.ts` from the directory of the config file instead of the current directory, so editor integrations in multi-root workspaces load the correct project. - Vite+ installs its own dependencies during setup and `vp upgrade` with `pnpm@10.34.9` (was `pnpm@10.34.7`). - The new Oxfmt and Oxlint can flag code that passed before. If your CI runs `vp check`, run `vp check --fix --continue-on-error` after you upgrade: it formats files, applies the available lint fixes, formats again, and reports every error that remains. For example, `unicorn/prefer-type-error` now also reports a `throw` in an `if` branch without braces, and this command rewrites it. ### Fixes & Enhancements - While a Vite+ spinner is visible, such as `Installing global packages` in `vp install -g`, Vite+ hides the cursor and discards typed keys. Pressing Enter no longer leaves copies of the spinner row, and typed text no longer runs in the shell after the command ends. Ctrl+C during a spinner now ends the command with the usual signal status instead of exit code 0, and the global package spinners show the elapsed time ([#3373](#3373), [#3417](#3417)), by @jong-kyung and @fengmk2. - `vp run` loads a package's `vite.config.*` only when the run reaches one of that package's tasks. A run in one package no longer waits for the configs of other packages, a broken config in another package no longer fails it, and `vp run <task>` in a package that does not define the task reports `Task "<task>" not found` instead of another package's config error ([vite-task#944](voidzero-dev/vite-task#944), [vite-task#988](voidzero-dev/vite-task#988)), by @wan9chi. - `vp run nope#build`, where no workspace package has the name `nope`, fails with `Package 'nope' not found in the workspace` and exits with code 1, instead of running nothing and exiting with code 0. A short name that matches several scoped packages fails as ambiguous ([vite-task#984](voidzero-dev/vite-task#984)), by @wan9chi. - Folder listings no longer skip entries named `dist`, so a `dist` folder that appears or disappears in a folder a task lists makes the next run a cache miss. Exclusions in a task's `input`, such as `"!dist/**"`, now also apply to the folders that the task lists. In a new monorepo from `vp create`, every task hits the cache from the third `vp run ready`, because the first build creates the `dist` folders ([vite-task#919](voidzero-dev/vite-task#919), [vite-task#941](voidzero-dev/vite-task#941)), by @wan9chi. - Fewer unnecessary cache misses and cache failures in `vp run`: on Windows, files that a task deletes or moves are no longer among its inputs. Tasks that read `node_modules/.vite/task-cache`, as Parcel and Gatsby do, hit the cache. A task that writes outside the workspace through `..`, like `cp -r dist ../site`, no longer fails with `Cache update failed` ([vite-task#937](voidzero-dev/vite-task#937), [vite-task#940](voidzero-dev/vite-task#940), [vite-task#980](voidzero-dev/vite-task#980)), by @wan9chi. - A cache hit restores the symbolic links that a task's `output` globs match as links, instead of dropping them ([vite-task#885](voidzero-dev/vite-task#885)), by @jasonkuhrt. - When several tasks become ready at the same time, `vp run` checks their cache entries in parallel, so cache hits start sooner ([vite-task#982](voidzero-dev/vite-task#982)), by @wan9chi. - On macOS, task commands that use `sh` or `bash` behave as on Linux: a `while read` loop with a redirect under `set -e` no longer exits the script, an `EXIT` trap sees the exit status, so a failed task is no longer reported as successful, and `$BASH` is set ([vite-task#939](voidzero-dev/vite-task#939)), by @lifeiscontent. - The helper files that `vp run` writes to the system temp directory go in one folder that only the current user can write to, such as `/tmp/vp_run-1000` on Linux. On Linux, a different Vite+ version run by another user no longer fails ([vite-task#947](voidzero-dev/vite-task#947), [vite-task#974](voidzero-dev/vite-task#974)), by @wan9chi. - A `getEnvs` query from `@voidzero-dev/vite-task-client` that matches every name (`{ prefix: '' }` or `*`) returns nothing and no longer adds every environment variable to the cache key ([vite-task#976](voidzero-dev/vite-task#976)), by @wan9chi. - `vp migrate` no longer writes package specs that the package manager cannot resolve, such as a `@vitest/*` `catalog:` reference without a catalog entry or a top-level catalog on Bun before 1.2.21. Bun projects with an empty `workspaces` field get catalog references, and child packages with a plain `vite-plus` range get the same concrete version as the root when the project cannot use catalogs ([#3397](#3397)), by @jong-kyung. - `vp create` uses the package manager version that `VP_PACKAGE_MANAGER` selects for the generated settings, the installation, and its summary. Standalone pnpm projects get `packages: ['.']` in an existing `pnpm-workspace.yaml` only for pnpm before 10.5.0 ([#3197](#3197)), by @evan-lc and @fengmk2. - `vp` sends a `User-Agent` header on all HTTP requests, so Node.js mirrors that reject requests without one, such as `mirrors.aliyun.com`, work ([#3425](#3425)), by @naokihaba. - `vp env pin` prints `Updated` when it overwrites an existing `.node-version` or `.nvmrc` file and `Created` when it writes a new one ([#3377](#3377)), by @CheHyeonYeong. ### Docs - Describe rebuildable inputs in the Automatic Data Tracking guide, and dry runs, JSON output, and `-vv` in the `vp run` guide ([#3419](#3419), [#3421](#3421)), by @wan9chi. ### Chore - Bump vite-task to `cb1ea8d`, with its user-facing changes listed above, and list `--dry-run`, `--json`, and `-vv` in `vp run --help` ([#3418](#3418)), by @wan9chi. - The daily dependency upgrade also updates the pnpm version that the installers pin, after it checks the release integrity ([#3407](#3407)), by @fengmk2. - Warm up the monorepo cache check in the `vp create` CI job under pnpm and Bun ([#3423](#3423)), by @wan9chi. - Remove an unused CI job that the required `done` check did not cover ([#3403](#3403)), by @jong-kyung. - Remove an incorrect comment about export pattern order in the CLI build script ([#3405](#3405)), by @alexicum. ### Bundled Versions | Tool | Version | Source | Changelog | | --------------- | ---------- | ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | vite | `8.3.7` | [`5def936`](vitejs/vite@5def936) | unchanged | | rolldown | `1.2.18` | [`f9a49d6`](rolldown/rolldown@f9a49d6) | unchanged | | oxc-node | `1.0.1` | [`7ff14c3`](oxc-project/oxc-node@7ff14c3) | unchanged | | tsdown | `0.23.4` | [npm](https://npmx.dev/package/tsdown/v/0.23.4) | unchanged | | vitest | `5.1.0` | [npm](https://npmx.dev/package/vitest/v/5.1.0) | unchanged | | oxlint | `1.93.0` | [npm](https://npmx.dev/package/oxlint/v/1.93.0) | [1.92.0](https://github.com/oxc-project/oxc/releases/tag/oxlint_v1.92.0), [1.93.0](https://github.com/oxc-project/oxc/releases/tag/oxlint_v1.93.0) | | oxlint-tsgolint | `7.0.2006` | [npm](https://npmx.dev/package/oxlint-tsgolint/v/7.0.2006) | [7.0.2006](https://github.com/oxc-project/tsgolint/releases/tag/v7.0.2006) | | oxfmt | `0.78.0` | [npm](https://npmx.dev/package/oxfmt/v/0.78.0) | [0.77.0](https://github.com/oxc-project/oxc/releases/tag/oxfmt_v0.77.0), [0.78.0](https://github.com/oxc-project/oxc/releases/tag/oxfmt_v0.78.0) | ### Upgrade ```bash vp upgrade ``` If `vp upgrade` must download Node.js and `VP_NODE_DIST_MIRROR` points to a mirror that rejects requests without a `User-Agent` header, such as `mirrors.aliyun.com`, unset it or point it to another mirror for this upgrade. The installed `vp` downloads Node.js and does not send the header yet. ### New Contributors @alexicum, @evan-lc, @CheHyeonYeong **Full Changelog**: v1.5.1...v1.6.0 --- For a stable release, complete the `HomebrewFormula/vp.rb` update after publication by merging the generated `release/homebrew-v1.6.0` PR. Merging this PR will trigger the release workflow. --------- Co-authored-by: voidzero-guard[bot] <278573678+voidzero-guard[bot]@users.noreply.github.com> Co-authored-by: MK (fengmk2) <fengmk2@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Motivation
A task that lists a folder holding its own outputs pins those outputs as entries of the listing. TypeScript 7's
tscwith noinclude, for example, lists the package root that holds itsliboutput folder. A clean checkout lacks them, so it misses. Today only an entry nameddistis spared, by a hard-coded skip.Changes
When a listing is fingerprinted, the entries the task can rebuild are left out and their names recorded with the listing: a file or symlink it wrote, or a rebuildable folder. The listing becomes
PathFingerprint::Folder(Option<DirListing>), withDirListing { entries, ignored_entries }, so only a listing can carry ignored names. Validation drops the same names from the current listing before comparing, so they may be missing or present. Any other entry that differs still misses and is named. On file systems that don't report entry types, an entry's kind is looked up withfstatat, so listings and the folder climb agree. The cache schema version is bumped.E2E cases:
list_folder_holding_output(synthetic; an unrelated new file still misses) andtypescript_lib_out_dir(TypeScript 7,outDir: "lib").Part of a stack that lets automatic tracking cache tasks which read their own outputs and list the folders holding them, so they also hit on a clean checkout.
🤖 Generated with Claude Code
Note
Medium Risk
Changes post-run fingerprint semantics and invalidates existing cache entries (schema v21), which affects cache hit/miss correctness for any task that lists directories containing its outputs.
Overview
When a cached task lists a parent folder that also contains its outputs, those rebuildable files and output-only subfolders no longer appear in the stored directory listing. Their names are kept in
ignored_entries, and cache validation strips the same names from the live listing before comparing, so a clean checkout withoutlib,gen/, etc. can still cache hit and replay restores outputs.PathFingerprint::Foldernow wrapsDirListing { entries, ignored_entries }instead of a plain entry map;CACHE_SCHEMA_VERSIONis bumped to 21.Rebuildablegainsis_rebuildable_entry(and related helpers) so listing fingerprinting matches the existing “output-only folder” logic. On Unix, directory entries without a reported type are classified viafstatat, aligning listings with rebuildable-folder detection.New e2e fixtures cover synthetic “list package root after writing
gen/” andtscwithoutDir: lib;typescript_incrementalis no longer Unix-only now that listing behavior is generalized.Reviewed by Cursor Bugbot for commit c7a32cb. Bugbot is set up for automated code reviews on this repo. Configure here.