Opened 5 years ago

Closed 2 years ago

#15648 closed enhancement (wontfix)

Create Protobufs for OONI's test reports

Reported by: isis Owned by: hellais
Priority: Medium Milestone:
Component: Archived/Ooni Version:
Severity: Normal Keywords: ooni, ooni-pipeline, protobufs, bridgedb-parsers, archived-closed-2018-07-04
Cc: isis, hellais, aagbsn Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


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.

Child Tickets

Change History (2)

comment:1 Changed 3 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:2 Changed 2 years ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: newclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.