Bind GLM runtimes to recurrent tail publication - #145
Closed
FujitsuPolycom wants to merge 10 commits into
Closed
Conversation
Compose both adaptive-MTP and DFlash7 Python-overlay images from SparkCache 08e2977 and the hash-proven recurrent-boundary vLLM producer. Require the producer label in resolved profiles, preserve fail-closed runtime attestation, and move the adaptive executable quickstart onto the capable builder.\n\nCache namespace impact: none. CacheIdentity values, digest salts, 256-token geometry, page-delta wire bytes, and the page-tail-cow-v1 namespace are unchanged. The lease-contract bytes advance so the exact recurrent producer postimages are accepted.\n\nValidation: exact source context prepare and verify passed; Ruff passed; GPU-free CI scope 1,973 passed, 9 skipped.
The PR35 lease contract requires recurrent producer symbols, so it cannot verify the intermediate source after only the SparkCache 041 patch. Run the single lease verification after the recurrent patch creates all required symbols and exact postimages.\n\nAdd GPU-free ordering coverage that requires the producer application and definitions to precede the only lease-verifier invocation.\n\nValidation: exact context prepare/verify passed; 1,974 passed, 9 skipped; Ruff passed.
Advance both GLM Python-overlay builders and executable profiles to SparkCache 49c517e and final lease contract f36ed14. Context preparation now executes SparkCache's strict lease verifier against the exact fully composed vLLM tree after all recurrent postimages exist.\n\nCache namespace impact: none. CacheIdentity values, digest salts, 256-token geometry, page-delta bytes, manifest schemas, and page-tail-cow-v1 remain unchanged.\n\nValidation: exact context prepare/verify and real final lease verifier passed; 1,975 passed, 9 skipped; Ruff passed.
Treat the composed verification report as one exact DFlash member plus an independent exact set of four recurrent postimages. Reject malformed, duplicate, missing, altered, or unexpected records.\n\nValidation: focused overlay/profile contracts 47 passed; Ruff passed. The broad GPU-free run passed 1,975 tests and hit one unrelated Windows atomic-status-file PermissionError; that isolated test passed immediately.
Mamba cache_blocks can receive a finalized token count beyond the replay boundary. Queue the hash-proven page when that boundary block enters the newly cached range instead of requiring num_tokens to equal it. Repin both GLM Python-overlay runtimes, profiles, and quickstarts to SparkCache 972b203 and its exact crossing-aware lease contract. Cache namespace impact: none. SparkCache identities, digest salts, 256-token geometry, manifest schemas, page-delta bytes, and page-tail-cow-v1 are unchanged. Validation: exact context preparation and eleven-file verifier passed; focused overlay/profile tests 47 passed; maintained-tree test run reached 1,975 passes with one corrected stale-pin failure; Ruff and diff checks passed.
An overshooting Mamba manager call has already nulled the earlier arithmetic page, so the attempted crossing predicate could not produce hash-proven state. Restore the exact-stop producer and fail closed for direct overshoot callers. Repin both runtimes and executable profiles to SparkCache bf7174e, which keeps the all-groups proof latch while restoring the verified f67 producer contract. Cache namespace impact: none. SparkCache identities, digest salts, 256-token geometry, manifests, page deltas, and page-tail-cow-v1 are unchanged.
Advance both GLM Python-overlay runtimes and executable profiles to SparkCache bd3eec1. The consumer now ignores valid earlier recurrent checkpoints while waiting for an exact later publication boundary, including the 6912 proof observed before the 8192 partial-tail CoW hand-off. The verified vLLM producer, scheduler regressions, lease contract, and cache namespace are unchanged. Validation: exact context preparation and repeat verification passed; maintained SparkRing scope 1976 passed, 9 skipped; Ruff and diff checks passed.
Advance both GLM Python-overlay runtimes and executable profiles to SparkCache c56f77f. Future recurrent proof remains rejected, and the diagnostic source now records its observed boundary, target boundary, group, and block. The verified vLLM producer and scheduler behavior are unchanged. Validation: exact context preparation and repeat verification passed; maintained SparkRing scope 1976 passed, 9 skipped; Ruff and diff checks passed.
Owner
Author
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
1 participant
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.
Outcome
This stack binds the adaptive-MTP and DFlash7 Python-overlay runtimes to SparkCache's fail-closed recurrent publication state machine and the exact vLLM producer behavior.
SparkCache commit c56f77f97b3da907d32e888d82046359a62f0f88 latches a complete validated mapping for every recurrent group. Outputs without a per-request entry leave publication pending. Incomplete, malformed, conflicting, or changed evidence cancels the attempt. The nonaligned 8,192-token page is published only from vLLM's pinned next-step CoW destination, never from an accumulated source-table ID.
The vLLM producer remains the exact verified patch SHA-256 5a6561a5bbab990dcd03bfd6a485ea26c3b5a578c2fd61b76305767b16dbfba0 with single_type postimage f67a1850a7e0288baaa6d42e7ec55b22b09c156720767e23acaabedcae333c8a. An overshooting direct Mamba-manager call emits no mapping because the prior arithmetic slots are null; it does not guess. Real Scheduler.schedule regressions cover the 7-token speculative path: 6,656 computed tokens schedule to the exact 6,912 aligned stop and emit its mapping in the same output; 7,936 schedule to the 8,192 partial boundary with no first-output hand-off, then the next one-token step CoWs and emits the destination mapping. Pin cleanup is verified.
Both runtime builders, executable profiles, labels, source receipts, and quickstarts use the same exact contract.
Exact identities
Cache namespace impact
None. CacheIdentity values, digest salts, 256-token geometry, page-delta bytes, manifest schemas, and page-tail-cow-v1 are unchanged. Unproven state remains unpublished and recomputes.
Validation
No image was built or published. No service, container, or serving host was changed.