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
  • #7938

Closed
Open
Opened Jan 12, 2013 by Karsten Loesing@karsten

Add parsing support for bridge network statuses to Stem

When parsing bridge descriptor tarballs, Stem doesn't like the contained network statuses:

ParsingFailure: Unrecognized metrics descriptor format. type: 'bridge-network-status', version: '1.0'

This format isn't as explicitly defined as the formats of other network statuses. Bridge network statuses start with a "@type bridge-network-status 1.0" line, followed by a "published" line, followed by router status entries, not followed by any kind of footer. This format is produced by metrics-db as part of the sanitizing process. If we were to specify it more explicitly, we should add a new section after the sanitized bridge descriptor specification.

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#7938