-
Notifications
You must be signed in to change notification settings - Fork 16
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
Netx research and refactoring in Sprint 15 #646
Labels
Milestone
Comments
4 tasks
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
We need this to reimplement the telegram experiment in terms of the urlgetter experiment, to simplify the code. See #646.
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
We need this to reimplement the telegram experiment in terms of the urlgetter experiment, to simplify the code. See #646.
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
With the Multi urlgetter you can perform operations in parallel with a specific degree of parallelism. You get results back as they arrive via a channel that is returned on output. We'll use this functionality pretty much soon to rewrite the Telegram experiment in terms of the urlgetter experiment. Reference issue: #646
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
With the Multi urlgetter you can perform operations in parallel with a specific degree of parallelism. You get results back as they arrive via a channel that is returned on output. We'll use this functionality pretty much soon to rewrite the Telegram experiment in terms of the urlgetter experiment. Reference issue: #646
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
This is less error prone. I consider this yak shaving to make the code more robust before continuing with #646.
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
This is less error prone. I consider this yak shaving to make the code more robust before continuing with #646. While there reduce linter warnings.
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
This will be useful to more easily classify the cause of blocking. This is part of #646
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
This will be useful to more easily classify the cause of blocking. This is part of #646
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
This is very useful to quickly understand what actually went wrong. It is a facet of the next design that was never really used. Also, acknowledge that, in some cases, there isn't a real failed operation because the error happens before we enter into our network stack. This happens, for example, when the context we're using is canceled. To address this potential issue, introduce and use a `"top_level"` operation that describes this specific situation. This work is part the telegram rewrite: #646. Also, with this diff landing we can close #311, which mentioned oonimkall (the old implementation of netx) but is still basically talking about the same concept we're implementing here.
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
This is very useful to quickly understand what actually went wrong. It is a facet of the next design that was never really used. Also, acknowledge that, in some cases, there isn't a real failed operation because the error happens before we enter into our network stack. This happens, for example, when the context we're using is canceled. To address this potential issue, introduce and use a `"top_level"` operation that describes this specific situation. This work is part the telegram rewrite: #646. Also, with this diff landing we can close #311, which mentioned oonimkall (the old implementation of netx) but is still basically talking about the same concept we're implementing here.
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
We often need to check the status code of the last response in the chain and/or to see the body of such response. To simplify these use cases, introduce two new variables that contain such values. These variables are not JSON serialised, because it does not make sense for us to do that. One can always recompute these fields, and the point of this patch is just to avoid duplicating code. Added an extra integration test to make sure that the value of these new variables is okay not only when the context is canceled but also when we're not doing HTTP but something else, e.g., just TLS. Part of #646. We will use this new code to simplify post processing of Telegram results.
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
We often need to check the status code of the last response in the chain and/or to see the body of such response. To simplify these use cases, introduce two new variables that contain such values. These variables are not JSON serialised, because it does not make sense for us to do that. One can always recompute these fields, and the point of this patch is just to avoid duplicating code. Added an extra integration test to make sure that the value of these new variables is okay not only when the context is canceled but also when we're not doing HTTP but something else, e.g., just TLS. Part of #646. We will use this new code to simplify post processing of Telegram results.
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
Like for MK errors, use the same naming of the C++11 library. This error will happen when the mobile app will interrupt specific tests, so better to have a clear naming for it. Part of #646.
bassosimone
added a commit
to ooni/spec
that referenced
this issue
Jun 9, 2020
Introduced in ooni/probe-engine#682 Part of ooni/probe-engine#646
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
Like for MK errors, use the same naming of the C++11 library. This error will happen when the mobile app will interrupt specific tests, so better to have a clear naming for it. Part of #646.
bassosimone
added a commit
to ooni/spec
that referenced
this issue
Jun 9, 2020
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
This was referenced Jun 9, 2020
bassosimone
added a commit
that referenced
this issue
Jun 9, 2020
Part of #646 Passes all checks from ooni/jafar#28
1 task
We have now refactored Telegram. More work in next sprint: #684. |
bassosimone
added a commit
to ooni/jafar
that referenced
this issue
Jun 9, 2020
Update deps and adapt to current miniooni Part of ooni/probe-engine#646 Used to validate ooni/probe-engine#683
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following up from #576
experiment/telegram
usingexperiment/urlgetter
"context canceled"
so it gets scrubbedexperiment/telegram
in terms ofexperiment/urlgetter
This refactoring is functional to measure performance metrics. In turn, by doing that we will be able to measure HTTP fetching performance metrics for Psiphon. This is also a precondition to rewrite Web Connectivity in Go.
The text was updated successfully, but these errors were encountered: