Repository navigation
Retain complete bounded diagnostics for failed package commands - #505
Merged
Merged
Conversation
hanthor
marked this pull request as ready for review
September 27, 2026 17:46
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.
The c49 hosted package trial produced the exact 322-package baseline, then an offline APT install returned nonzero. The command runner raised before retaining its buffered output, and the failure record contained a truncated argv string. This prevented diagnosis of the actual package failure.
Retain the numeric exit status and complete bounded command streams. Failure-only serial chunks carry full size and SHA256 references, so the owned observer can reconstruct fixed output files even when QGA is unavailable. Keep the failure record small and retain the full bounded serial alongside reconstructed streams before process cleanup. These records never grant package acceptance.
Validation: 115 native runtime controls passed, including six command-failure controls, real nonzero subprocess output, invalid UTF-8, maximum binary output through the actual observer and artifact exporter, and malformed/missing/duplicate/foreign-boot chunk refusal. Consumer 28 controls and runtime 77/classic 32 provenance audits passed. Removing actual subprocess stream retention made the control fail.
The original run 36336755778 remains failed. No new guest run or package, OS, or firmware acceptance is claimed by this draft.