Originally created by @github-actions[bot] on GitHub (Apr 17, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1363
Hourly sampling detected a content_hash mismatch between the production Worker and the release vault.db. This is a data-plane SLI alert — corpus content may be corrupted at the edge. Workflow: https://github.com/harvard-edge/cs249r_book/actions/runs/24550391329
Closing as stale / duplicate. Root cause: the vault-content-hash-sli workflow's Python probe threw ValueError: unknown url type before any hash compare step because WORKER_URL was unset (worker not yet deployed). The issue title ("content-hash SLI mismatch") was misleading — there was no mismatch, only an infra-config failure dressed as data corruption.
Fixed in #1384 by deleting the workflow outright rather than patching it. The SLI's design conflated build-output consistency with runtime integrity; the compiler's atomic write already provides the invariant it claimed to check. If runtime integrity becomes a real requirement later, the right architecture is signed responses + client verification, not hourly hash re-probing.
No new content-hash SLI mismatch issues should auto-file after this point.
<!-- gh-comment-id:4270166875 -->
@profvjreddi commented on GitHub (Apr 17, 2026):
Closing as stale / duplicate. Root cause: the `vault-content-hash-sli` workflow's Python probe threw `ValueError: unknown url type` before any hash compare step because `WORKER_URL` was unset (worker not yet deployed). The issue title ("content-hash SLI mismatch") was misleading — there was no mismatch, only an infra-config failure dressed as data corruption.
Fixed in #1384 by deleting the workflow outright rather than patching it. The SLI's design conflated build-output consistency with runtime integrity; the compiler's atomic write already provides the invariant it claimed to check. If runtime integrity becomes a real requirement later, the right architecture is signed responses + client verification, not hourly hash re-probing.
No new `content-hash SLI mismatch` issues should auto-file after this point.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @github-actions[bot] on GitHub (Apr 17, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1363
Hourly sampling detected a content_hash mismatch between the production Worker and the release vault.db. This is a data-plane SLI alert — corpus content may be corrupted at the edge. Workflow: https://github.com/harvard-edge/cs249r_book/actions/runs/24550391329
@profvjreddi commented on GitHub (Apr 17, 2026):
Closing as stale / duplicate. Root cause: the
vault-content-hash-sliworkflow's Python probe threwValueError: unknown url typebefore any hash compare step becauseWORKER_URLwas unset (worker not yet deployed). The issue title ("content-hash SLI mismatch") was misleading — there was no mismatch, only an infra-config failure dressed as data corruption.Fixed in #1384 by deleting the workflow outright rather than patching it. The SLI's design conflated build-output consistency with runtime integrity; the compiler's atomic write already provides the invariant it claimed to check. If runtime integrity becomes a real requirement later, the right architecture is signed responses + client verification, not hourly hash re-probing.
No new
content-hash SLI mismatchissues should auto-file after this point.