Preserve diagnostics for installer failures before backend startup - #58
Merged
Merged
Conversation
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.
An installed app can fail before its backend opens a listener. The smoke test previously recorded no startup diagnostics in that case and cleanup removed the remaining logs. Preserve the process exit state and bounded, redacted shell/backend log excerpts before cleanup, and upload the failed report from release CI.
The existing startup deadline and publication gates remain unchanged. The PowerShell module is exercised through a checked-in helper, including exited/running processes, missing and locked logs, redaction, and truncated input.
Validation: 160 focused tests; Ruff lint and format checks over maintained Python sources; Actionlint. The unchanged v0.5.119 candidate also passed clean installation, upgrade, frontend, support, five media checks and strict uninstall in diagnostic run 35364030659. That successful reproduction does not identify the original timeout's cause.