Conversation
fspy benchmarklinuxmacoswindows |
Remote cache stagingCommit: Cloudflare staging deployment and smoke tests passed. You can now perform manual verification. Endpoint: https://vp-cache-ci-staging.voidzero-docs.workers.dev/projects/manual Download the remote-cache-e2e-37270185172-1 artifact from the workflow run. It contains PR checks cover public reads and rejected writes. Main-branch push checks also cover authorized HTTP stores. This staging endpoint is shared by all PRs and main. A later deployment replaces its code and manual fixture. Compare the deployment ID in the response with the artifact before manual verification. Closing this PR does not remove staging. |
3454480 to
845fb3c
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
…rker The e2e backend was a Node file backend that imitated a remote cache server's protocol and write policy. Behind the same `remote-cache-server` commands, it's now Vite+'s Cloudflare implementation, from voidzero-dev/vite-plus-remote-cache-cloudflare at a pinned commit, in workerd through Miniflare: - The Worker runs with the compatibility settings, bindings, and limits that wrangler reads from its `wrangler.jsonc`, with its namespaces limited to the endpoint's. - As in a deployment, every migration is applied with wrangler's SQL splitter, and the namespace is registered for the endpoint and the test repository. - The Worker fetches GitHub's key set to verify upload tokens, and gets the GitHub Actions stand-in's key instead. Any other outbound request fails. - `corrupt-blob` replaces the blob's object in R2. The workspace now allows the build scripts of esbuild and workerd, which a root `pnpm install` otherwise rejects. None of the snapshots change. The cases that use the backend are now skipped on musl, because workerd's prebuilt binaries require glibc. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
845fb3c to
f097c29
Compare
Motivation
The remote cache e2e cases ran against a Node file backend that imitated a remote cache server's protocol and write policy. #807 → #810 put the test infrastructure in place against that backend: one backend per case, a tap for the request log, blob numbering,
corrupt-blob, and a GitHub Actions stand-in. Vite+'s Cloudflare implementation now lives in voidzero-dev/vite-plus-remote-cache-cloudflare, moved there from #718, and the cases can run against it: a real, independently written server for the protocol.Changes
remote-cache-servercommands, the backend is that Worker at a pinned commit, a git dependency ofvite-task-tools, running in workerd through Miniflare:wrangler.jsonc. Its namespaces are limited to the endpoint's.corrupt-blobreplaces the blob's object in R2 and its recorded size.pnpm installotherwise rejects.@cloudflare/workers-typesprovides Miniflare's binding types.@fastify/busboydependency.None of the snapshots change. The daemon, the tap, the CLI, and the stand-in are untouched. Only the backend behind them is different.
Stacked on #810.
🤖 Generated with Claude Code