-
Notifications
You must be signed in to change notification settings - Fork 142
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
torsf: TestRunWithExistingTor hangs forever #2540
Comments
This diff makes the policy previously known as loadable and now know as the static policy easier to use, by having a constructor that reads from a key-value store and by passing it a fallback policy to use. With this design, it should be possible to have code that uses the static policy if applied, falling back to whatever policy we are otherwise constructing into the NewNetwork constructor. In a subsequent commit, I will hook this code into NewNetwork, so that we can override the policy by changing the filesystem. While there, notice several failures in the test suite and apply workarounds (see ooni/probe#2539, ooni/probe#2540, ooni/probe#2541). Part of ooni/probe#2531.
Probably, this is the same issue as: https://forum.torproject.org/t/problems-with-snowflake-since-2023-09-20-broker-failure-unexpected-error-no-answer/9346 |
We're doing this due to problems with `cdn.sstatic.net`: - https://lists.torproject.org/pipermail/anti-censorship-team/2023-September/000315.html - https://forum.torproject.org/t/problems-with-snowflake-since-2023-09-20-broker-failure-unexpected-error-no-answer/9346 The reference issue is ooni/probe#2540. While there, fix a typo in a test name. --------- Co-authored-by: Simone Basso <[email protected]>
We have fixed the underlying issue (thanks @cohosh!). And I am going to close this PR. However, I am not very fond of how much static configuration is embedded into the probe source code. I'm wondering of whether there is a way for us to have the check-in API tell us which is the proper SNI for Snowflake. This would reduce the need to release frequently. In any case, this topic is probably best being addressed as a new, separate issue. |
…#1297) This diff makes the policy previously known as loadable and now know as the static policy easier to use, by having a constructor that reads from a key-value store and by passing it a fallback policy to use. With this design, it should be possible to have code that uses the static policy if applied, falling back to whatever policy we are otherwise constructing into the NewNetwork constructor. In a subsequent commit, I will hook this code into NewNetwork, so that we can override the policy by changing the filesystem. While there, notice several failures in the test suite and apply workarounds (see ooni/probe#2539, ooni/probe#2540, ooni/probe#2541). Part of ooni/probe#2531.
We're doing this due to problems with `cdn.sstatic.net`: - https://lists.torproject.org/pipermail/anti-censorship-team/2023-September/000315.html - https://forum.torproject.org/t/problems-with-snowflake-since-2023-09-20-broker-failure-unexpected-error-no-answer/9346 The reference issue is ooni/probe#2540. While there, fix a typo in a test name. --------- Co-authored-by: Simone Basso <[email protected]>
The
TestRunWithExistingTor
test runs for a long time (probably ~forever) and logs these messages:I am going to disable this integration test, but we must fix this issue before releasing 😅 .
To reproduce:
go test -run TestRunWithExistingTor -v -count 1 ./internal/experiment/torsf
The text was updated successfully, but these errors were encountered: