Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #22990

Closed (moved)
Open
Opened Jul 20, 2017 by Karsten Loesing@karsten

Add a heartbeat log message indicating progress and estimated time left

It would be really useful to know how long it still takes to read a bunch of descriptors, as this can range from minutes to hours or even days. In some cases this information would help to decide whether to continue or abort and try something different.

How about we start reading descriptors by walking files in the given directories, summing up their bytes, and using that total sum to periodically write a log message with progress and estimated time left?

Once per minute on debug level would be sufficient. And it's okay if it's not super precise and gets confused by compression or other factors. Just a rough number that gets more precise over time.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#22990