-
Notifications
You must be signed in to change notification settings - Fork 32
fix: ignore disableCache in client #481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
24 changes: 14 additions & 10 deletions
24
...shots/disable_cache_forces_reexecution.md → ...ts/disable_cache_noop_allows_cache_hit.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,40 +1,44 @@ | ||
| # disable_cache_forces_reexecution | ||
| # disable_cache_noop_allows_cache_hit | ||
|
|
||
| Exercises `disableCache`. The tool asks the runner not to cache this run, | ||
| so the next invocation re-executes instead of hitting a prior entry. | ||
| Exercises the temporary `disableCache` no-op workaround. The tool asks the | ||
| runner not to cache this run, but the client ignores that request, so the next | ||
| invocation hits the cache. | ||
|
|
||
| ## `vt run disable-cache` | ||
|
|
||
| first run — tool calls disableCache | ||
| first run — tool calls disableCache, currently ignored by the client | ||
|
|
||
| ``` | ||
| $ node scripts/disable_cache.mjs | ||
| ``` | ||
|
|
||
| ## `vt run disable-cache` | ||
|
|
||
| cache miss (NotFound) because nothing was cached | ||
| cache hit because disableCache is temporarily a no-op | ||
|
|
||
| ``` | ||
| $ node scripts/disable_cache.mjs | ||
| $ node scripts/disable_cache.mjs ◉ cache hit, replaying | ||
|
|
||
| --- | ||
| vt run: cache hit. | ||
| ``` | ||
|
|
||
| ## `vt run --last-details` | ||
|
|
||
| summary names the opt-out as the not-cached reason | ||
| summary reports the replayed cache hit | ||
|
|
||
| ``` | ||
|
|
||
| ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ | ||
| Vite+ Task Runner • Execution Summary | ||
| ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ | ||
|
|
||
| Statistics: 1 tasks • 0 cache hits • 1 cache misses | ||
| Performance: 0% cache hit rate | ||
| Statistics: 1 tasks • 1 cache hits • 0 cache misses | ||
| Performance: 100% cache hit rate | ||
|
|
||
| Task Details: | ||
| ──────────────────────────────────────────────── | ||
| [1] ipc-client-test#disable-cache: $ node scripts/disable_cache.mjs ✓ | ||
| → Not cached: the task opted out of caching | ||
| → Cache hit - output replayed - | ||
| ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ | ||
| ``` |
23 changes: 14 additions & 9 deletions
23
...sable_cache_works_with_explicit_inputs.md → ...isable_cache_noop_with_explicit_inputs.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,39 +1,44 @@ | ||
| # disable_cache_works_with_explicit_inputs | ||
| # disable_cache_noop_with_explicit_inputs | ||
|
|
||
| Exercises `disableCache` on a cached task with explicit inputs. The runner must still inject IPC even when fspy auto-input inference is disabled, or the tool's cache opt-out becomes a no-op and the second run incorrectly hits. | ||
| Exercises the temporary `disableCache` no-op workaround on a cached task with | ||
| explicit inputs. The client ignores the opt-out request, so the second run hits | ||
| even when fspy auto-input inference is disabled. | ||
|
|
||
| ## `vt run disable-cache-explicit-input` | ||
|
|
||
| first run uses input: [] and asks the runner not to cache | ||
| first run uses input: [] and calls disableCache, currently ignored by the client | ||
|
|
||
| ``` | ||
| $ node scripts/disable_cache.mjs | ||
| ``` | ||
|
|
||
| ## `vt run disable-cache-explicit-input` | ||
|
|
||
| re-executes because the first run was not cached | ||
| cache hit because disableCache is temporarily a no-op | ||
|
|
||
| ``` | ||
| $ node scripts/disable_cache.mjs | ||
| $ node scripts/disable_cache.mjs ◉ cache hit, replaying | ||
|
|
||
| --- | ||
| vt run: cache hit. | ||
| ``` | ||
|
|
||
| ## `vt run --last-details` | ||
|
|
||
| summary names the opt-out as the not-cached reason | ||
| summary reports the replayed cache hit | ||
|
|
||
| ``` | ||
|
|
||
| ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ | ||
| Vite+ Task Runner • Execution Summary | ||
| ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ | ||
|
|
||
| Statistics: 1 tasks • 0 cache hits • 1 cache misses | ||
| Performance: 0% cache hit rate | ||
| Statistics: 1 tasks • 1 cache hits • 0 cache misses | ||
| Performance: 100% cache hit rate | ||
|
|
||
| Task Details: | ||
| ──────────────────────────────────────────────── | ||
| [1] ipc-client-test#disable-cache-explicit-input: $ node scripts/disable_cache.mjs ✓ | ||
| → Not cached: the task opted out of caching | ||
| → Cache hit - output replayed - | ||
| ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ | ||
| ``` |
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
25 changes: 25 additions & 0 deletions
25
...ite_dev_disable_cache/snapshots/vite_dev_disable_cache_noop_allows_cache_hit.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| # vite_dev_disable_cache_noop_allows_cache_hit | ||
|
|
||
| `vt run --cache dev` brings up a Vite dev server programmatically on an | ||
| ephemeral port and closes it immediately. Vite calls `disableCache()` via | ||
| `@voidzero-dev/vite-task-client`, but the client temporarily ignores that | ||
| request, so the next invocation hits the cache. | ||
|
|
||
| ## `vt run --cache dev` | ||
|
|
||
| first run — Vite dev calls disableCache, currently ignored by the client | ||
|
|
||
| ``` | ||
| $ node dev.mjs | ||
| ``` | ||
|
|
||
| ## `vt run --cache dev` | ||
|
|
||
| cache hit because disableCache is temporarily a no-op | ||
|
|
||
| ``` | ||
| $ node dev.mjs ◉ cache hit, replaying | ||
|
|
||
| --- | ||
| vt run: cache hit. | ||
| ``` |
19 changes: 0 additions & 19 deletions
19
..._snapshots/fixtures/vite_dev_disable_cache/snapshots/vite_dev_disables_cache.md
This file was deleted.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this new
Ok(())path, public clients no longer sendRequest::DisableCache, but the include-ignored e2e fixture still asserts thatdisableCache()forces the next run to miss; runningcargo test -p vite_task_bin --test e2e_snapshots -- --include-ignored disable_cache_forces_reexecutionnow fails because the second run is a cache hit. Please update or remove the affectedipc_client_test/vite_dev_disable_cachesnapshots alongside this behavior change so the documented Node-client suite matches the new contract.Useful? React with 👍 / 👎.