Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Collector
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • 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.

  • The Tor Project
  • Metrics
  • Collector
  • Issues
  • #22834

Closed
Open
Opened Jul 06, 2017 by iwakeh iwakeh@iwakeh

Decide what to do with UnparseableDescriptors while synchronizing from another instance

Let's find out, if a code change is needed or things are fine as they are.

Current situation when one CollecTor fetches data from another CollecTor: Metrics Lib cannot parse the fetched content, provides an object of UnparseableDescriptor, and CollecTor simply ignores this object as unknown (only logs on trace level).

During normal collecting an unparseable descriptor is stored anyway.

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: tpo/metrics/collector#22834