Repository navigation
Retain the first AT RSS budget failure census - #702
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.
The AT supervisor currently reports a sampled RSS cap failure without retaining the per-process sample that triggered it. Native run 38155201280/a1 exceeded the unchanged 2 GiB cap by 44,740,608 bytes; its retained artifact records the aggregate peak but cannot identify the actor at that peak.
Retain the first authenticated owned sample and supervisor birth/RSS when the existing guard refuses. Bound the diagnostic to 1,024 owned rows and 1,024 known births, with explicit omitted counts. Snapshot, integrity and result-report failures preserve the RSS primary cause; custody uncertainty keeps its separate diagnostic. The existing diagnostic self-test covers resource failure, snapshot/hash/cleanup/report failures, and the below/equal-cap boundaries with inert child/proc samples.
Qualification: the bounded Python-only operation passed all 29 source-coupled navigation controls and the existing diagnostic self-test, including the seven new RSS failure/boundary cases. Original owner receipts matched, custody qualified with observed-empty cleanup, and source pins remained unchanged. This source change does not establish native journey success or change the resource cap.