Repository navigation
Release 1.0.1: bound command output and child cleanup - #11
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
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.
Unbounded command output and cleanup could exhaust memory or hold command execution after its deadline. Enforce a combined 4 MiB stdout/stderr limit, initialize the selector before launch, and bound child cleanup even when stream registration fails.
Update release metadata, operational limits, Docker/Compose instructions and regenerated capture metadata. The image now installs the published Auton/autond 1.3.2 OIDC fix. Existing return-code and deployment-failure behavior stays covered.
Complete the existing tested publication chain: main selects an immutable version tag only after unit/lifecycle/Debian/build gates, publishes the same distributions to PyPI and GitHub, then validates amd64/arm64 Compose before Docker publication. Existing environments, secrets and tag protection remain in place; already-tagged later commits do not republish. Preserve prerelease tags and skip stable Docker publication for prereleases.
Validation: 246 unit tests and 11 contracts passed; release helper suite 19 collected (18 passed, one existing pytest-only collection sentinel skipped); strict Sphinx build passed; CLI/TUI captures regenerated and inspected. CI must pass before merge.
CI follow-up: the standalone lifecycle run initially timed out waiting for the scheduler's held HTTP-01 challenge (run 39589770331, attempt 1). Its unchanged retry passed. The independent publication-chain lifecycle on the same commit also passed, as did both Debian/systemd lifecycle checks. No assertion or deadline was relaxed; the initial intermittent failure is retained and its precise cause is not established.
All current PR gates are green, including minimum/latest dependencies, actual served TLS and failure recovery, Debian/systemd, documentation captures and amd64/arm64 Compose.