You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit eb94686
Browse filesBrowse the repository at this point in the historyBrowse files
cache: load remote fetches directly into the CAS by declared checksum
A remote fetch with a declared sha256 doesn't need the action cache:
the checksum is itself a content address. Make the CAS hash-function
aware — blobs live at cas/<function>/<xx>/<hash>, keyed by BLAKE3 by
default — and add PutSHA256/SHA256Digest so remotely fetched content is
stored and looked up directly under the checksum declared in the
configuration, with the checksum re-verified on every read.
The WASM plugin path drops its FetchPlugin action entirely; the action
cache now backs only work whose outputs aren't derivable from its
inputs, like query analysis. This mirrors Bazel, where downloads go
through the checksum-addressed repository cache rather than the action
cache.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MPgq3rwip76D554BktbqR4
0 commit comments