Repository navigation
Seal Harness generation inputs before execution registration - #475
Draft
zengchuang-hw wants to merge 1 commit into
Draft
zengchuang-hw wants to merge 1 commit into
zengchuang-hw wants to merge 1 commit into
Conversation
Signed-off-by: zengchuang <zengchuang3@huawei.com> Agent-assisted-by: Codex (author)
This was referenced Nov 16, 2026
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.
Governing issue and proposal
Refs #447
Refs #371
This draft implements the proposed pre-registration retention transaction from the storage handoff for Harness owner review. The current
Claim.commitrequires the final request digest to register the attempt. V24 computes that digest after binding the retained generation manifest.inferrsi.harness.generation.prepare_generationcalls the injected Apps ContextProvider, verifies the actual bytes and commits them with the delivery metadata in RunStore. It hands the committed delivery to CandidateProvider, commits the resulting GenerationManifest and returns the final ExecutionSpec with itsgeneration_planinput.Verification
Five focused tests passed. They cover failure before staging and after staging but before commit, no visible delivery/manifest on those failures, cross-process reread of the delivered bytes and pins, successful CPU execution, replay of the original attempt, immutable delivery and retry after a manifest commit failure. The broader Windows regression on
cc9b2206passed with 127 tests and 43 subtests, with two POSIX-only skips. Repository Ruff and the staged diff check passed.