1
72%
master: 72%

Ran 28 Sep 2023 11:25AM UTC

Files 511

Run time 9s

Badge

Embed ▾

Committed 28 Sep 2023 11:20AM UTC coverage: 81.958% (+0.02%) from 81.941%

Job # 6338187301.1

Build Type

push

github

Committed by

web-flow

Commit Message

feat(model): introduce ArchivalBinaryData (#1321)

There are cases where we know we have binary data in input and we want
the output to be binary data using the dictionary encoding like
`{"format":"base64","data":"..."}`.

Such cases are, for example, DNS messages bodies.

There is no need for us to pass through the MaybeArchivalBinaryData in
such cases. Additionally, this makes MaybeArchivalBinaryData a bit more
complex than it probably needs to be.

What's more, ArchivalBinaryData is for when you do not require to scrub
the data. I want to introduce new data types that automatically perform
scrubbing when they're used.

But this puts even more pressure on MaybeArchivalBinaryData, and hence
this commit, to start differentiating between:

1. always binary data vs maybe binary data

2. no scrubbing required vs scrubbing required

The rationale for doing this set of changes has been explained in
https://github.com/ooni/probe-cli/pull/1319.

The reference issue is https://github.com/ooni/probe/issues/2531.

For now, this commit just adds the new type and tests for it without
using the type, which we'll do later once we have added better
marshal/unmarshal testing for the interested types.

Run Details

24267 of 29609 relevant lines covered (81.96%)

35.18 hits per line

ooni / probe-cli / 6338187301 / 1
72%
master: 72%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 0 - 6338187301.1

ooni / probe-cli / 6338187301 / 1 72% master: 72%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 0 - 6338187301.1

ooni / probe-cli / 6338187301 / 1
72%
master: 72%

README BADGES
x