Skip to content
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

cli: fix table in Tor anomalous measurements #1698

Open
agrabeli opened this issue Apr 19, 2021 · 4 comments
Open

cli: fix table in Tor anomalous measurements #1698

agrabeli opened this issue Apr 19, 2021 · 4 comments
Assignees
Labels
bug Something isn't working correctly data quality priority/low Nice to have

Comments

@agrabeli
Copy link
Member

I noticed that in some anomalous Tor measurements, the table (which displays an overview of results based on the testing of Tor directory authorities and Tor bridges) is inaccurate -- in comparison to the raw data.

For example, look at this measurement: https://explorer.ooni.org/measurement/20210416T000625Z_tor_AZ_39232_n1_cLbrywxhrppEuk7l

It says that connections to only 3/10 Tor directory authorites were successful (and this is corroborated in the raw data), but the UI of the table includes a tick next to each tested directory authority.

See:

tor-table

This seems like a bug. We therefore need to fix the table so that it accurately displays which connections to Tor directory authorities (and bridges) failed.

@sarathms
Copy link

sarathms commented Jun 19, 2021

@bassosimone I am using test_keys.targets[${address}].summary.connect.failure (for the 'Connect' column). And then if (that.failure === null) I stamp that target with ✅ or if it has a string then ❌. If this is a wrong interpretation, what is a right one?

@sarathms sarathms assigned bassosimone and unassigned sarathms Jun 23, 2021
@sarathms sarathms transferred this issue from ooni/explorer Jun 23, 2021
@sarathms sarathms added the triage Should be triaged through the triage board label Jun 23, 2021
@bassosimone bassosimone changed the title Fix table in Tor anomalous measurements cli: fix table in Tor anomalous measurements Jun 23, 2021
@bassosimone
Copy link
Contributor

We looked into this with @sarathms and this is a bug in probe-cli, so we moved the issue into the probe repository.

@sarathms
Copy link

The particular target that has a clearer issue in the sample measurement is 45.66.33.45:443

image

@bassosimone bassosimone added effort/L priority/medium Normal priority issue bug Something isn't working correctly and removed triage Should be triaged through the triage board labels Jul 6, 2021
@bassosimone bassosimone added priority/high Important issue that needs attention soon and removed priority/medium Normal priority issue labels Nov 11, 2021
@hellais hellais removed the effort/L label Jan 31, 2022
@bassosimone
Copy link
Contributor

So, on re-reading this issue, I don't think this is a probe bug, rather it's an UI bug that we should figure out how to address. The column is named "connect" and the tick means that we could connect. The error presented above says that the TLS handshake failed with a "generic timeout error".

What I find wrong about the table generated by https://explorer.ooni.org/measurement/20210416T000625Z_tor_AZ_39232_n1_cLbrywxhrppEuk7l is that there is no information about the handshake in all cases, which does not strike me as correct.

@hellais hellais added this to Roadmap Jan 7, 2025
@hellais hellais added priority/low Nice to have and removed priority/high Important issue that needs attention soon labels Jan 23, 2025
@hellais hellais moved this to Backlog in Roadmap Jan 23, 2025
@hellais hellais assigned majakomel and DecFox and unassigned bassosimone Jan 23, 2025
@hellais hellais removed this from Roadmap Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working correctly data quality priority/low Nice to have
Projects
None yet
Development

No branches or pull requests

6 participants