A Void build misses the vp run cache on a fresh checkout unless its inputs are listed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- build-system
Research direction
Start by reading the automatic input tracking and cache rules for void build, then trace where the build creates .void/, .wrangler/, and .void-wrangler.jsonc in the project directory. Related issue #492 and vite-plus#3113 provide context for the cache rules. Done means generated files no longer make the tracked input listing differ between a fresh checkout and a cached build, without requiring explicit cache.input.
Written by the indexing model from the issue text.
Description
Filed by Claude Opus 5.5 on behalf of @anaclumos under explicit approval
Seen with Void 1.3.0 under vp run from Vite+ 1.4.0, with automatic input tracking.
On a fresh checkout, a void build task run through vp run misses the cache unless the task lists its cache.input explicitly.
The cause:
-
The build creates
.void/,.wrangler/, and.void-wrangler.jsoncin the project directory. -
The tracker records the project directory's listing as an input.
-
A cached build's recorded listing therefore never matches a fresh checkout's listing.
-
Expected: Void's generated files stay out of the tracked inputs, for example under an output directory or declared as task outputs, so a fresh checkout can replay a cached build.
-
Workaround: list the build's
cache.inputexplicitly.
Related: #492, whose automatic tracking of Void builds depends on the unreleased rebuildable cache rules in voidzero-dev/vite-plus#3113.
- Dominant language
- TypeScript
- Stars
- 580
- Forks
- 56
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 158
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from voidzero-dev/void
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
voidzero-dev/void#638 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
voidzero-dev/void#635 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
voidzero-dev/void#627 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
voidzero-dev/void#619 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
voidzero-dev/void#606 ·
Maintainers usually reply within 1 day
All issues in voidzero-dev/void
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Graphify-Labs/graphify#4860 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sveltejs/eslint-plugin-svelte#1615 ·
Maintainers usually reply within 7 days
-
Parallel reticle_verify opens per-flow leases without the source lease's ignoreHTTPSErrorsPossibly taken @as992949791 claimed this today. Opengood first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
reticlehq/reticle#2033 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day