Conversation
wan9chi
force-pushed
the
remote-cache-hit-source
branch
from
September 24, 2026 19:46
8d89f96 to
00bacf6
Compare
wan9chi
added this pull request to stack #751
September 24, 2026 19:46
fspy benchmarklinuxmacoswindows |
wan9chi
force-pushed
the
remote-cache-hit-source
branch
from
September 25, 2026 02:04
00bacf6 to
d9ec5a7
Compare
wan9chi
force-pushed
the
remote-cache-hit-source
branch
2 times, most recently
from
September 25, 2026 02:28
acbe343 to
0f57cb9
Compare
wan9chi
force-pushed
the
remote-cache-hit-source
branch
from
September 25, 2026 02:29
0f57cb9 to
527f703
Compare
wan9chi
removed this pull request from stack #751
September 25, 2026 02:34
wan9chi
added this pull request to stack #759
September 25, 2026 02:35
wan9chi
force-pushed
the
remote-cache-hit-source
branch
from
September 25, 2026 02:38
527f703 to
33bfa6a
Compare
wan9chi
force-pushed
the
remote-cache-hit-source
branch
from
September 25, 2026 03:07
33bfa6a to
21f0eca
Compare
A cache hit now records whether it came from the local or the remote cache. Remote hits are marked inline (`◉ remote cache hit, replaying`), in the compact summary (`vp run: remote cache hit, 1s saved.` for a single task, `2/3 cache hit (66%, 1 remote)` otherwise), in the full summary's statistics (`2 cache hits (1 remote)`), and in the task details (`→ Remote cache hit - output replayed - 1s saved`). Local hits look as before. The saved summary records the source, and summaries saved without it read as local hits. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
wan9chi
force-pushed
the
remote-cache-hit-source
branch
from
September 25, 2026 04:12
21f0eca to
6e5fd41
Compare
This branch has not been deployed
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
#756 restores task results from the remote cache, but a remote hit looks the same as a local one. Showing where a hit came from makes it clear that the remote cache is working and how much of a run it served.
A cache hit now records whether it came from the local or the remote cache. Remote hits are marked, and local hits look as before:
$ vtt write-file dist/output.txt built ◉ remote cache hit, replayingvp run: remote cache hit, 1.2s saved.vp run: 2/2 cache hit (100%, 1 remote).--last-detailsstatistics:Statistics: 2 tasks • 2 cache hits (1 remote) • 0 cache misses--last-detailstask details:→ Remote cache hit - output replayed - 1.2s savedThe saved summary records the source for
--last-details. A summary saved without it reads as local hits.The
restoresnapshot now shows the remote hit, and a new ignoredlocal_and_remote_hitscase runs a remote hit and a local hit together, followed by--last-details.