Skip to content

Conversation

@frankmcsherry
Copy link
Member

Attempt at logging operator summaries (the internal matrix of input->output timestamp summaries describing the operator's internal connectivity). I mostly copied existing code, and .. once this is up I'll be able to have a better look and see if it makes any sense. It roughly follows #624 which did something similar for progress and reachability logging, though I may have erred in important ways.

Copy link
Member

@antiguru antiguru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, I left some comments!

identifier: usize,
logging: Option<Logger>
logging: Option<Logger>,
summary_logging: &mut Option<SummaryLogger<T::Summary>>,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively Option<&mut SummaryLogger<...>>? I can't seem to ever know which one to use where, but here we don't want to change the option... Also, logging mightn't need mutable access iirc

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will address in a follow-up!

@frankmcsherry frankmcsherry merged commit 91e491f into TimelyDataflow:master Jan 21, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants