Repository navigation
fix(sessions): suppress unchanged Pi discovery summaries - #4552
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.
Change
Refs #4481. Suppress repeated aggregate Pi discovery warnings when the omitted failure count and retained evidence count have not changed. Reuse the existing bounded state-change log gate, keyed by sessions root. Full evidence or recovery clears the state, so a later recurrence logs again.
Individual discovery failures, malformed-source refusals, deferred outcomes and partial coverage remain unchanged. This does not implement scan quarantine or resolve the remaining CPU, GPU and storage symptoms.
Verification
Bazel executed both new regressions individually with one test passed each. The Pi test group passed 11 tests with zero failures or ignored tests. Scoped Clippy with warnings denied and the affected Rust formatting target passed. Independent source review accepted the logging-only slice. Commitlint and diff checks passed.
Local checks used the pinned toolchain and existing Cargo cache through supported Bazel offline resolution. No deadline, capacity or byte limit was raised. No operator profile or host configuration changed.