February 2019 - tor-commits - lists.torproject.org

[translation/support-portal] Update translations for support-portal
by translation＠torproject.org 15 Feb '19

15 Feb '19

commit 0f0f9050614286c6ccb03448431db27c3219d312 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 15 21:20:12 2019 +0000 Update translations for support-portal --- contents+fr.po | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/contents+fr.po b/contents+fr.po index ee2cc16e4..20f434f9e 100644 --- a/contents+fr.po +++ b/contents+fr.po @@ -758,7 +758,7 @@ msgid "" "connections. You can reconfigure or disable your … [View More]firewall and restart Tor to" " test this." msgstr "" -"Un firewall est un système de sécurité réseau qui surveille et contrôle le " +"Un firewall est un système de sécurité réseau qui surveille et contrôle " "trafic réseau entrant et sortant (#trafic). Ce filtre de trafic est basé sur" " des règles prédéterminées. Un firewall établit généralement une barrière " "entre un réseau interne sécurisé et fiable et un autre réseau externe, mais " @@ -1812,9 +1812,9 @@ msgid "" "receiver but only the receiver in possession of the private key is able to " "decrypt the message." msgstr "" -"N'importe qui peut [crypter](#encryption) un message en utilisant la clé " -"publique du destinataire mais seul le destinataire en possession de la clé " -"privée est capable de décrypter le message." +"N’importe qui peut [chiffrer](#encryption) un message en utilisant la clé " +"publique du destinataire, mais seul le destinataire, qui possède la clé " +"privée, peut déchiffrer le message." #: https//support.torproject.org/glossary/ #: (content/glossary/contents+en.lrquestion.description) @@ -2237,8 +2237,8 @@ msgid "" "software associated with this network is called Core Tor, and sometimes " "[\"little-t tor\"](#little-t-tor)." msgstr "" -"Cet ensemble de relais bénévoles s'appelle le réseau Tor. Parfois le " -"logiciel associé à ce réseau est appelé Core Tor, et parfois [\"little-t " +"Cet ensemble de relais bénévoles s'appelle réseau Tor. Parfois le logiciel " +"associé à ce réseau est appelé Core Tor, et parfois [\"little-t " "tor\"](#little-t-tor)." #: https//support.torproject.org/glossary/ @@ -3431,8 +3431,8 @@ msgstr "" #: (content/tbb/tbb-13/contents+en.lrquestion.title) msgid "Does using Tor Browser protect other applications on my computer?" msgstr "" -"L’utilisation du Navigateur Tor protège-t-elle les autres applications sur " -"mon ordinateur ?" +"L’utilisation du Navigateur Tor protège-t-elles autres applications sur mon " +"ordinateur ?" #: https//support.torproject.org/tbb/tor-browser-protecting-other-apps/ #: (content/tbb/tbb-13/contents+en.lrquestion.description) [View Less]

1 0

[translation/donatepages-messagespot_completed] Update translations for donatepages-messagespot_completed
by translation＠torproject.org 15 Feb '19

15 Feb '19

commit 3d2b141c1c6f6aa0ac52fac484c417daa530f315 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 15 21:15:36 2019 +0000 Update translations for donatepages-messagespot_completed --- locale/fr/LC_MESSAGES/messages.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/locale/fr/LC_MESSAGES/messages.po b/locale/fr/LC_MESSAGES/messages.po index f42954d09..7f9deccc3 100644 --- a/locale/fr/LC_MESSAGES/messages.po +++ b/locale/fr/LC_MESSAGES/… [View More]

1 0

[translation/donatepages-messagespot] Update translations for donatepages-messagespot
by translation＠torproject.org 15 Feb '19

15 Feb '19

commit 0af978af95ce861e0a4cd767758e117ed3f17960 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 15 21:15:27 2019 +0000 Update translations for donatepages-messagespot --- locale/fr/LC_MESSAGES/messages.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/locale/fr/LC_MESSAGES/messages.po b/locale/fr/LC_MESSAGES/messages.po index f42954d09..7f9deccc3 100644 --- a/locale/fr/LC_MESSAGES/messages.po +++ b/locale/fr/LC_MESSAGES/messages.po @… [View More]

1 0

[translation/donatepages-messagespot] Update translations for donatepages-messagespot
by translation＠torproject.org 15 Feb '19

15 Feb '19

commit 70e26aaa23ae8d48efadd5cc2a4af5011084172e Author: Translation commit bot <translation(a)torproject.org> Date: Fri Feb 15 18:45:27 2019 +0000 Update translations for donatepages-messagespot --- locale/sk/LC_MESSAGES/messages.po | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/locale/sk/LC_MESSAGES/messages.po b/locale/sk/LC_MESSAGES/messages.po index b4d9db7b5..cd1484a15 100644 --- a/locale/sk/LC_MESSAGES/messages.po +++ b/locale/sk/LC_MESSAGES/… [View More]

1 0

[sbws/master] fix: config: set stdout log level to cli argument
by juga＠torproject.org 15 Feb '19

15 Feb '19

commit 5c50636294066cc257f96f1a89c1515c8b8641a6 Author: juga0 <juga(a)riseup.net> Date: Thu Feb 7 08:46:49 2019 +0000 fix: config: set stdout log level to cli argument when the cli argument `log-level` is provided. Before, it was only setting the minimal log level, but it was not changing the stdout level. Closes: #29199. Bugfix v0.6.0. --- sbws/util/config.py | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/sbws/util/config.… [View More]

1 0

[sbws/master] Merge branch 'bug29199'
by juga＠torproject.org 15 Feb '19

15 Feb '19

commit a1926b88786bd01cf0a4f1f6c7014db3fea41a1e Merge: e23a25a 5c50636 Author: juga0 <juga(a)riseup.net> Date: Fri Feb 15 17:52:28 2019 +0000 Merge branch 'bug29199' sbws/util/config.py | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)

1 0

[sbws/master] relayprioritizer: remove asserts on hard-coded values
by juga＠torproject.org 15 Feb '19

15 Feb '19

commit ce08884f51b500d2dabaedf371dc2bf53bee0297 Author: juga0 <juga(a)riseup.net> Date: Tue Dec 18 09:07:47 2018 +0000 relayprioritizer: remove asserts on hard-coded values result.freshness_reduction_factor are hard-coded values, no need to assert. --- sbws/lib/relayprioritizer.py | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/sbws/lib/relayprioritizer.py b/sbws/lib/relayprioritizer.py index 318d1a8..9c065a7 100644 --- a/sbws/lib/… [View More]

1 0

[sbws/master] relayprioritizer: Stop prioritizing relays that tend to fail
by juga＠torproject.org 15 Feb '19

15 Feb '19

commit 96c718805cb7e0a6d3869e2b6b9ce7e6b94a55f3 Author: juga0 <juga(a)riseup.net> Date: Tue Dec 18 08:37:59 2018 +0000 relayprioritizer: Stop prioritizing relays that tend to fail Because unstable relays that often fail to be measured, might fail again and stable relays will get measured only when their measurements become old enough. Leave the possibility to still prioritize the relays that failed to be measured by having a function argument that defaults … [View More]to False. Rephrase docstring to reflect this situation. Fixes bug #28868. Bugfix v0.1.0 --- sbws/lib/relayprioritizer.py | 43 +++++++++++++++++++++++-------------------- 1 file changed, 23 insertions(+), 20 deletions(-) diff --git a/sbws/lib/relayprioritizer.py b/sbws/lib/relayprioritizer.py index 3a635f0..f17ebd4 100644 --- a/sbws/lib/relayprioritizer.py +++ b/sbws/lib/relayprioritizer.py @@ -23,28 +23,30 @@ class RelayPrioritizer: self.fraction_to_return = conf.getfloat( 'relayprioritizer', 'fraction_relays') - def best_priority(self): - ''' Return a generator containing the best priority relays. + def best_priority(self, prioritize_result_error=False): + """ + Return a generator of a new list of relays ordereded by priority to + be measured. The relays that were measured farther away in the past, + get prioritized (lowest priority number, first in the generator). - NOTE: A lower value for priority means better priority. Remember your - data structures class in university and consider this something like a - min-priority queue. + The relays that were measured more recently get lower priority (last in + the generator, higher priority number). - Priority is calculated as the sum of the "freshness" of each - result for a relay. First we determine <oldest_allowed>, the time at - which we stop considering results to be valid. From there, a result's - freshness is determined to be the amount of time between when the - measurement was made and <oldest_allowed>. Therefore, you should see - that a measurement made more recently will have a higher freshness. + Optionally, the measurements that failed can be prioritized (be + measured first). + However, unstable relays that often fail to be measured, might fail + again and stable relays will get measured only when their measurements + become old enough. + The opposite might be more suitable: give lower priority to the relays + that are unstable, to don't spend time measuring relays that might fail + to be measured. - We adjust down the freshness for results containing errors. If we - ignored errors and didn't increase a relay's priority value for them, - then we'll get stuck trying to measure a few relays that have the best - priority but are having issues getting measured. If we treated errors - with equal weight as successful results, then it would take a while to - get around to giving the relay another chance at a getting a successful - measurement. - ''' + Since measurements made before than X days ago (too old) are not + considered, and the initial list of past measurements is only filtered + when the scanner starts, it's needed to filter here again to discard + those measurements that are too old. + + """ fn_tstart = Decimal(time.time()) relays = set(copy.deepcopy(self.relay_list.relays)) if not self.measure_authorities: @@ -63,7 +65,8 @@ class RelayPrioritizer: # Calculate freshness as the remaining time until this result # is no longer valid freshness = result.time - oldest_allowed - if isinstance(result, ResultError): + if isinstance(result, ResultError) \ + and prioritize_result_error is True: # Reduce the freshness for results containing errors so # that they are not de-prioritized as much. This way, we # will come back to them sooner to try again. [View Less]

1 0

[sbws/master] relayprioritizer: add argument to return only a fraction
by juga＠torproject.org 15 Feb '19

15 Feb '19

commit 133e37ba47eadfbff545e03c87673bb99781db9b Author: juga0 <juga(a)riseup.net> Date: Tue Dec 18 08:57:02 2018 +0000 relayprioritizer: add argument to return only a fraction Not all the relays in the network are returned by this method, but a fraction of them. Create an argument to allow to change this default behaviour to return all the relays in the network. --- sbws/lib/relayprioritizer.py | 50 +++++++++++++++++++++++++++++++------------- 1 file changed, 35 … [View More]insertions(+), 15 deletions(-) diff --git a/sbws/lib/relayprioritizer.py b/sbws/lib/relayprioritizer.py index f17ebd4..963d08a 100644 --- a/sbws/lib/relayprioritizer.py +++ b/sbws/lib/relayprioritizer.py @@ -23,28 +23,45 @@ class RelayPrioritizer: self.fraction_to_return = conf.getfloat( 'relayprioritizer', 'fraction_relays') - def best_priority(self, prioritize_result_error=False): - """ - Return a generator of a new list of relays ordereded by priority to - be measured. The relays that were measured farther away in the past, - get prioritized (lowest priority number, first in the generator). + def best_priority(self, prioritize_result_error=False, + return_fraction=True): + """Yields a new ordered list of relays to be measured next. + The relays that were measured farther away in the past, + get prioritized (lowest priority number, first in the list). The relays that were measured more recently get lower priority (last in - the generator, higher priority number). + the list, higher priority number). - Optionally, the measurements that failed can be prioritized (be - measured first). - However, unstable relays that often fail to be measured, might fail + Optionally, the relays which measurements failed can be prioritized + (first in the list). + However, unstable relays that fail often to be measured, might fail again and stable relays will get measured only when their measurements become old enough. The opposite might be more suitable: give lower priority to the relays that are unstable, to don't spend time measuring relays that might fail to be measured. + Optionally, return only a fraction of all the relays in the network. + Since there could be new relays in the network while measuring the + list of relays returned by this method, this method is run again + before all the relays in the network are measured. + + .. note:: + + In a future refactor, instead of having a static fraction of relays + to be measured, this method could be call when it's known that + there're X number of new relays in the network. + Since measurements made before than X days ago (too old) are not considered, and the initial list of past measurements is only filtered when the scanner starts, it's needed to filter here again to discard - those measurements that are too old. + those measurements. + + :param bool prioritize_result_error: whether prioritize or not + measurements that did not succed. + :param bool return_fraction: whether to return only a fraction of the + relays seen in the network or return all. + return: a generator of the new ordered list of relays to measure next. """ fn_tstart = Decimal(time.time()) @@ -82,14 +99,17 @@ class RelayPrioritizer: # Sort the relays by their priority, with the smallest (best) priority # relays at the front relays = sorted(relays, key=lambda r: r.priority) - cutoff = max(int(len(relays) * self.fraction_to_return), - self.min_to_return) + fn_tstop = Decimal(time.time()) fn_tdelta = (fn_tstop - fn_tstart) * 1000 log.info('Spent %f msecs calculating relay best priority', fn_tdelta) - # Finally, slowly return the relays to the caller (after removing the - # priority member we polluted the variable with ...) - for relay in relays[0:cutoff]: + + # Return a fraction of relays in the network if return_fraction is + # True, otherwise return all. + cutoff = max(int(len(relays) * self.fraction_to_return), + self.min_to_return) + upper_limit = cutoff if return_fraction else len(relays) + for relay in relays[0:upper_limit]: log.debug('Returning next relay %s with priority %f', relay.nickname, relay.priority) del(relay.priority) [View Less]

1 0

[sbws/master] relayprioritizer: remove unneded assert
by juga＠torproject.org 15 Feb '19

15 Feb '19

commit 25967c0a34564515cfbae848b727171d7bc45663 Author: juga0 <juga(a)riseup.net> Date: Tue Dec 18 09:02:25 2018 +0000 relayprioritizer: remove unneded assert --- sbws/lib/relayprioritizer.py | 2 -- 1 file changed, 2 deletions(-) diff --git a/sbws/lib/relayprioritizer.py b/sbws/lib/relayprioritizer.py index 963d08a..318d1a8 100644 --- a/sbws/lib/relayprioritizer.py +++ b/sbws/lib/relayprioritizer.py @@ -1,6 +1,5 @@ from decimal import Decimal from ..lib.resultdump import … [View More]

1 0