Repository navigation
perf(proximity): use bounded caller adjacency for qualitative hints - #4790
ScriptedAlchemy wants to merge 12 commits into
Conversation
Avoid materializing graph-impact reports for relationship hints. Refuse incomplete caller closures instead of treating them as absent. Refs #4416
|
Exercise exact-budget test identity retention, failed caller reads at all three hops, and empty adjacency without additional graph reads. Refs #4416
|
Published The exact parent-to-commit diff contains only test additions; publication used |
Skip outgoing second-hop reads for roots whose adjacency was already fetched in the first hop. Preserve the reached-root relationship evidence while avoiding redundant graph queries and exhausting fewer read budgets. Add regressions for connected roots and self-/cross-root cycles; previous behavior issues redundant reads and fails those assertions. Refs #4416
Evaluate complete shared-caller adjacency before lower-priority outgoing second-hop dependencies. Preserve an already-proven caller hint when an unneeded dependency lookup would refuse its read budget. Keep direct relation precedence, bounded seed coverage, and cached first hops. Add two behavioral regressions that require no dependency queries for shared callers, and exact second-hop reads for real shared dependencies. Refs #4416
Preserve a shared third-hop affected-test relationship when the later higher-priority dependency closure refuses a read. Mark the known positive hint partial instead of publishing no relation; complete shared-dependency evidence still takes precedence. Factor the existing test metadata fixture and add nonzero behavioral regression covering left/right second-hop refusal, short-circuit read counts, and successful dependency precedence. Refs #4416
Apply all eleven exact rustfmt corrections reported by the hosted Repository gates on the existing issue-specific PR. No intended behavior changes; preserve every concurrent graph repair. Refs #4416
Use std::slice::from_ref in the real dependency traversal regression. This resolves the exact blocking -D warnings diagnostic reported by hosted Clippy on the current PR head; test behavior stays unchanged. Refs #4416
Apply the exact source changes requested by the first failing hosted Bazel Rustfmt gate at the preceding PR head. No behavior or assertions change; all existing regression tests are preserved. Refs #4416 Verification: source contexts checked against hosted Rustfmt diffs. New-head Rust/Bazel tests require hosted CI.
Issue
Refs #4416 — focused graph-neighborhood correctness/performance slice, not full issue acceptance. No Kev/decision-model work.
Implementation
graph.impact()reports for qualitative caller/test hints with bounded, generation-pinnedcallers()batches; preserve depth-2 caller hints, depth-3 test evidence, and independent two-hop dependencies.1826d405,2f0930f4).cb30baf8: reuse the already-fetched outgoingcallees()first-hop batches from direct relationship checks in the transitive dependency closure. Avoid two redundant first-hop graph reads for a path pair requiring both sides' transitive analysis.Verification
cb519ba: when a direct dependency points to another selected graph seed, reuse that seed's already-fetched adjacency during the two-hop closure. Preserve discovered root/cycle evidence without a redundant second-hop query. Two new falsifiable Rust regressions assert exact second-hop frontiers for connected roots and zero extra reads for self-/cross-root cycles. This one-file patch was diff-reviewed againstb5ad368(43 added/6 deleted), appended without force under the expected old head, preserving all peer commits.cb519ba1654bf5b4060ad5cbdf64e7d97cc7f3ff, this PR changes onlycrates/tracedecay-application/src/advisory/proximity_runtime/authority.rs. The previous updates remain in history. The latest commit is a child ofb5ad368and was published withforce=falseand a matching expected-old-head lease.1826d405: hosted Bazel run 42433277177 had nonzero passing application tests, but the broader Linux fleet failed three automation-scheduler tests outside this file.2f0930f4: run 42437742003 was still in progress when this metadata was updated. It cannot verify the new change.Latest correctness/performance repair (2026-11-08)
21898591b38fmoves the complete shared-caller test ahead of second-hop outgoing dependency expansion. Previously, an over-budget or failed unused dependency read could erase an already-proven higher-precedence shared-caller relationship. It also avoided useful unnecessary graph work.cb519baand was pushed withforce=falseand a matching expected-old-head check. The exact 199-addition/88-deletion diff was source-reviewed. No new Rust/Bazel test pass is claimed; hosted CI on this head is required.Remaining acceptance
#4416 remains open: numeric threshold/configuration/schema/UI retirement and Loom/feedback end-to-end verification are separate outstanding acceptance. No "Fixes" closure or merge is claimed here. PR-maintenance handles eligible CI/merges; held draft #4776 and beta.99 #4763 remain untouched.
Preserved affected-test evidence on incomplete dependency reads
Commit
2fd8d4bfadds a correctness repair: when both three-hop incoming caller closures have proved an affected test, a later incomplete second-hop outgoing read now retains that positive SharedTest hint marked Partial. Successful, complete shared-dependency evidence still wins its higher warning-class precedence. Previously the later refusal suppressed an already-proven test relationship entirely.The new nonzero behavioral regression exercises failed left and right second-hop reads (with exact early-stop read counts) and successful shared-dependency precedence. The existing depth-three test metadata fixture was factored, not weakened. One-file diff against old head
21898591was independently inspected; 127 insertions / 35 deletions (including the fixture move). Update was a non-force expected-head fast-forward, preserving all existing commits.Verification: the new Rust regression has not yet executed via Bazel. No native macOS evidence is claimed. CI for the current head must demonstrate nonzero
//crates/tracedecay-application:unit_testand:application_suiteand all relevant gates; keep #4416 open (numeric threshold/schema/UI retirement and Loom journey are not addressed here).Hosted rustfmt gate repair
Commit
cbbf871applies all 11 exact formatting hunks reported by the previous-head Repository gates. The repair was assembled from the actual pinned Rustfmt job log, validated against each unique source context, and independently compared with the prior head (one file, 49 additions / 25 deletions); no intended behavioral change. Published by nonforce fast-forward with expected old head2fd8d4bf. This fixes the observed format drift only: exact-new-head hosted Bazel format/Rust tests still require nonzero execution and passing results before merge.Latest CI repair — Clippy (2026-11-08)
Commit
f32face1replaces the single unnecessary cloned reference in the dependency-neighborhood Rust test withstd::slice::from_ref(&direct). The prior-head CI run 42457473999 passed Repository gates but failed Clippy atauthority.rs:1525(cloned_ref_to_slice_refsunder-D warnings). The expected-old-headcbbf871was confirmed and the update fast-forwarded withforce=false; compare shows one test file, one insertion and one deletion. No assertions were weakened. Full Rust/Bazel tests and native macOS remain unverified on this new head; the issue staysRefs #4416and open.Latest CI source fix — hosted Rustfmt (2026-11-08)
Commit
8bae143aapplies the one exact Rustfmt hunk reported by Repository gates in prior exact-head CI run 42461760176: theassert_eq!in the graph dependency regression is formatted into the required multi-line expression. The diff is one file, five insertions/one deletion; no assertions or production behavior changed. Independently reviewed the patch against the hosted job diff and fast-forwarded under the verified old head without force. New-head Bazel/Rust tests have not yet executed; no test pass or issue completion is claimed. Separate Clippy run at the prior head also suffered504 Gateway Time-outfetching hermetic-launcher prebuilt artifacts, so its failure is not a verified Rust-source error. #4416 still needs the numeric threshold/schema/UI retirement and Loom journey.