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

Expose the STUNReachability experiment #137

Closed
wants to merge 7 commits into from
Closed

Conversation

bassosimone
Copy link
Member

@bassosimone bassosimone commented Jun 8, 2020

Closes ooni/probe#1185.

@bassosimone bassosimone requested a review from hellais June 8, 2020 14:01
if tk["failure"] != nil {
testKeys.IsAnomaly = true
testKeys.Failure, ok = tk["failure"].(string)
failure, ok := tk["failure"].(*string)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I found out that this pattern needed to be changed when testing stunreachability

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the same change perhaps needed also for BootstrapTime?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No: BootstrapTime is not nullable. The issue here is that casting to *string and casting to string is not the same and we need to use the precise type. As for BootstrapTime it's float64 so we're good.

Make sure dependencies of probe-engine are at the same exact version to
which is probe-engine, to avoid any possible issue.
@bassosimone bassosimone changed the title Run stunreachability as part of the circumvention group Use probe-engine@v0.13.0 to add stun_reachability to the circumvention group Jun 10, 2020
Copy link
Member

@hellais hellais left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should consider adding support for running the test, but not showing it in the UI.

The way by which it's being added to probe-cli makes it so it's also going to be exposed in the UI, which I thought was not what we wanted.

Screenshot 2020-06-11 at 13 20 33

@bassosimone
Copy link
Member Author

@hellais I think it's fine that CLI users see it. What do desktop user see?

@hellais
Copy link
Member

hellais commented Jun 11, 2020

I tested this in the desktop app and it appears that it will in fact ignore the stun test result, but the counter for the number of tools is inconsistent (it says 3 instead of 2):

Screenshot 2020-06-11 at 14 51 20

I think the best way to go about doing this is to omit writing any sort of information about the results of this test to database at all and ensure that the output is identical to the output without this test.

@bassosimone
Copy link
Member Author

We'll put this PR on hold until we fix the issue of bad names in the database.

@bassosimone
Copy link
Member Author

bassosimone commented Jun 15, 2020

@hellais I've changed the PR so that we don't run STUNReachability. So, we can get the benefits of the latest probe-engine, but we are not running the test. (Deleting the existing code or opening a new PR looked like not needed to me; I'm open to create a new PR if you consider instead that doing that would be more proper form for proceeding.)

We'll put this PR on hold until we fix the issue of bad names in the database.

I think this should not prevent merging this PR. We should instead start integrating it and then possibly perform another small update to make sure we've a good DB.

@bassosimone bassosimone changed the title Use probe-engine@v0.13.0 to add stun_reachability to the circumvention group Upgrade to ooni/probe-engine@v0.13.0 Jun 15, 2020
@hellais
Copy link
Member

hellais commented Jun 15, 2020

I created a new epic and child issues for this:
ooni/probe#1202
This involves:

@bassosimone bassosimone changed the title Upgrade to ooni/probe-engine@v0.13.0 Expose the STUNReachability experiment Jun 15, 2020
@bassosimone
Copy link
Member Author

This branch now just contains the STUNReachability code. The part related to updating the version of ooni/probe-engine and to fixing Psiphon code landed as part of #138

@bassosimone
Copy link
Member Author

I have added STUN to the experimental nettest group in #243. This PR is now obsolete.

@bassosimone bassosimone closed this Mar 8, 2021
@bassosimone bassosimone deleted the issue/1185 branch March 8, 2021 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants