Logging nice-to-haves · Issue #114 · TimelyDataflow/timely-dataflow (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

We are about to land a PR #92 that overhauls the logging infrastructure. This issue keeps track of desirable features that should be possible with this infrastructure, but aren't yet designed/implemented.

• re-introduce the log crate
• allow ad-hoc logging of user code (i.e. allow users of timely to produce logging streams of a type picked by them)
• support log filtering, and selectively enabling log statements
• make sure that log streams can be flushed when necessary
• remove the time crate
• determine what timestamp resolution scale is appropriate, consider using a synchronisation point between processes as the time base for the logs
• let users toggle logging for certain dataflows