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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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

Closed
Open
Opened Apr 09, 2015 by Isis Lovecruft@isis

Create Protobufs for OONI's test reports

I am worried that randomly adding/removing/changing fields in the .yamloo OONI test report files is going to break report parsers in horrible ways. And YAML doesn't have the safest track history for its parsers either.

Perhaps we could have something like Protobufs for guaranteed marshaling/unmarshaling/parsing of report data? Setting up Protobufs for the reports would establish requirements, for example, that field names and data types/representations can't just randomly change in the future, at least not without bumping up the version for the report Protobuf (and thus regenerating the parsers/marshalers) and maintaining backwards-compatibility.

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