Repository navigation
Log each operator's frontier interest with its summary - #836
Merged
frankmcsherry merged 1 commit intoNov 8, 2026
Merged
Conversation
`OperatesSummaryEvent` gains `notify`, one `FrontierInterest` per input, taken from `notify_me()` where the summary is already logged. A region's entry is the strongest interest among its children, and at least `IfCapability`. Joined with `OperatesEvent` names, this shows which operators are scheduled as frontiers move, and which child keeps a region awake. `FrontierInterest` derives `Serialize`, `Deserialize` and `Columnar` so it can be logged. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Operator summaries now log each input's frontier interest, so a user can audit which operators are scheduled as frontiers move.
OperatesSummaryEventgainsnotify: Vec<FrontierInterest>, one entry per input, read fromnotify_me()at the point where the summary is already logged.This follows the summary's own shape, which already carries per-port information for the whole operator.
A region's entry is the strongest interest among its children, and at least
IfCapability, so joining withOperatesEventnames shows which child keeps a region awake.FrontierInterestderivesSerialize,DeserializeandColumnarso that it can be logged.For
input -> region { map -> inspect_core } -> probethe summaries reportFlatMap: [Never],Inspect: [Always],Region: [Always], andProbe: [Always]; without theinspect_corethe region reports[IfCapability].The new test checks these, and the mdbook's logging chapter describes the field.
This changes the fields of a public log event, so code that constructs or exhaustively matches
OperatesSummaryEventneeds updating.🤖 Generated with Claude Code