-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(datafmt): sync measurexlite and v0.5 with previous code #942
Conversation
Basically, `t0` and `transaction_id` should be optional. Version 0.4.x of web_connectivity should not include them, version 0.5.x should. There is a technical reason why v0.4.x should not include them. The code it is based on, tracex, does not record these two fields. Whereas, v0.5.x, uses measurexlite, which records these two fields. Part of ooni/probe#2238
This diff adds the following fields to webconnectivity@v0.5: 1. agent, always set to "redirect" (legacy field); 2. client_resolver, properly initialized w/ the resolver's IPv4 address; 3. retries, legacy field always set to null; 4. socksproxy, legacy field always set to null. Part of ooni/probe#2238
The general idea behind this field is that we would be able in the future to tweak the data model for some fields, by declaring we're using a later version, so it seems useful to add it. See ooni/probe#2238
This diff fixes a bug where measurexlite was using "tls" as the protocol for the TLS handshake when using TCP. While this choice _could_ make sense, the rest of the code we have written so far uses "tcp" instead. Using "tcp" makes more sense because it allows you to search for the same endpoint across different events by checking for the same network and for the same endpoint rather than special casing TLS handshakes for using "tls" when the endpoint is "tcp". See ooni/probe#2238
Let's break down how
Everything is good up to this point.
This test is failing because the address used by GitHub isn't included into the ASN database we're using. 😭
Everything above is WAI.
Again, we see failures because the ASN geolocation fails. Based on these results I think the following:
|
#942) * fix(model/archival.go): more optional keys Basically, `t0` and `transaction_id` should be optional. Version 0.4.x of web_connectivity should not include them, version 0.5.x should. There is a technical reason why v0.4.x should not include them. The code it is based on, tracex, does not record these two fields. Whereas, v0.5.x, uses measurexlite, which records these two fields. Part of ooni/probe#2238 * fix(webconnectivity@v0.5): add more fields This diff adds the following fields to webconnectivity@v0.5: 1. agent, always set to "redirect" (legacy field); 2. client_resolver, properly initialized w/ the resolver's IPv4 address; 3. retries, legacy field always set to null; 4. socksproxy, legacy field always set to null. Part of ooni/probe#2238 * fix(webconnectivity@v0.5): register extensions The general idea behind this field is that we would be able in the future to tweak the data model for some fields, by declaring we're using a later version, so it seems useful to add it. See ooni/probe#2238 * fix(measurexlite): use tcp or quic for tls handshake network This diff fixes a bug where measurexlite was using "tls" as the protocol for the TLS handshake when using TCP. While this choice _could_ make sense, the rest of the code we have written so far uses "tcp" instead. Using "tcp" makes more sense because it allows you to search for the same endpoint across different events by checking for the same network and for the same endpoint rather than special casing TLS handshakes for using "tls" when the endpoint is "tcp". See ooni/probe#2238 * chore: run alltests.yml for "alltestsbuild" branches Part of ooni/probe#2238
We're bumping the version number to reflect recent improvements in the data format implemented in these pull requests: - #942 - #943 - #944 Reference issue: ooni/probe#2238
chore: web_connectivity v0.5.5 We're bumping the version number to reflect recent improvements in the data format implemented in these pull requests: - #942 - #943 - #944 Reference issue: ooni/probe#2238
chore: web_connectivity v0.5.5 We're bumping the version number to reflect recent improvements in the data format implemented in these pull requests: - #942 - #943 - #944 Reference issue: ooni/probe#2238
This diff is the first step towards ooni/probe#2238. Let us make sure that new code uses the same data format of previously existing code. Once we're sure about this fact, we can update ooni/spec.