Since when a destination fails, all the threads using it will also
fail that moment.
For now not checking which threads are actually using it.
Also lower the time to retry.

Closes: #29891.

Part of #29589.

for each relay and for the list of relays when fetching new
network statuses.
To count the number of times a relay was in a consensus and how
many consensuses have been seen.
In the test network router status entries don't have document
attribute.
Part of #28566

Part of #29591.

Add methods to store consecutive destination failures and retrieve
the destinations that are still functional.
Since destinations can fail because of Tor circuits, it's not count
individual failures but consecutives one.
Also exit with error if there are no functional destinations left.
The maximum number of consecuitve failures is set to 10, but it
may need to be changed depending on the percentage of circuits and
requests that fail.

and create function to set options that can fail because they are
not supported by some Tor versions at runtime.

Fixes bug 28692. Bugfix v0.4.0

to a function.
Replace comment by docstring.
Add an integration test to check the option is set.

create a constant, set the headers in the session.

certificate by default.

They were used to resolve the IP of the destination and check
whether an exit policy allows to exit to that IP, but when the
destination is a CDN, the IP locally resolved would be different
to the IP resolved in the exit, and when the IP resolved to
IPv6, it was possible that the scanner didn't have IPv6.
The correct method to check whether an exit policy allows to exit
to an IP, would be to resolve the domain via Tor itself using
RESOLVE and ADDRMAP events with that exit.

Fixes bug #28646. Bugfix v0.4.0

Closes #28645. Bugfix v0.2.0.

Implements part of proposal 276.

Implements 28451.

Also go back to use sbws datadir as the default location for the
tor temporal file sockets, because when XDG_RUNTIME_DIR is not
set, the interpolation does not happen.

When the difference between the total consensus bandwidth and the
total in the bandwidth lines is larger than 50%, warn

Even for a valid domain that usually resolves, sometimes the local DNS
resolver won't be able to resolve it (duh). Catch the exception that gets
thrown in that instance and fail gracefully by returning an empty list.

and the min num of secs that the results must be away from each
other.

This required a bump in the result version: we add a new field to
ResultSuccess.

Matt Traudt authored Jun 07, 2018 and juga committed Jun 10, 2018

node_id=$B058ABB695524A11D0FE958C0F8AA7963FD4258C bw=5685 nick=exit2 rtt=139 time=2018-06-08T01:06:27 ed25519=g+Shk00y9Md0hg1S6ptnuc/wWKbADBgdjT0Kg+TSF3s

Matt Traudt authored Jun 07, 2018 and juga committed Jun 10, 2018

With unused support for ed25519 keys

also, convert types to int when generating line from str

* Move logic in generate to class
* Add test
* Move 7500 to global constant
* Make read_started_at not fail when conf is None

Also:
* add latest_bandwidth header
* add file_created header
* fix bw files header tests
* disable tests that assume timestamp to be the file creation
time
* if we use ISO 8601 with T as separator,
  datetime format string is not needed

timestamps

GH: closes #135