since deb.torproject.org does not support anymore Trusty.

so that CI doesn't fail because of timeout trying to retrieve the
key.

Closes #28922. Bugfix v1.0.3-dev0

Since the data for the tests and the torflow scaling method was
changed in #bug28598, ajust the values after merging #28602.

Torflow's scaling now round digits according to Proposal 276,
but for compatibility with Torflow's round digits algorithm,
the argument option has to be available and by default be
Proposal 276.

The torflow-round-digs cli argument was kept, but it was added
other argument, round-digs, for the same option.
argparse takes the first argument as the variable name, but the
methods where still using torflow_round_digs.

Closes bug #28602. Bugfix 1.0.3-dev0.

Destinations' Web servers must support TLS to avoid contents cache.

Fixes bug #28789. Bugfix v0.2.0.

Add a tox environment to check the links and call it from travis.
It's not run by tox in order to do not need Internet running tox.
The environment clean is also call from travis, in order to have
sphinx installed when checking the links.

Closes #28670.

Closes bug #28736. Bugfix v0.3.0.

The error that is returned by an exception, not a custom error.
So that it's easier to debug what fails.

bandwidth or rtt, so that it can be used to be stored and logged.

since it takes some seconds.

since it takes some seconds and the operator would not see any
progress at the beginning, until relays start to be measured.

When a new loop starts and when it ends, with the number of relays
measured and the time it took.

Warnings can make think the operator that sbws is not working,
while it's normal that some measurements fail.
Resultdump already logs at info level what succcess and what fails.
Keep these logs at debug level.

obtained when trying to build the circuit, or None if it was
successful.
That way it can be logged and stored in the results.

If rtt is configured to 0, the rtt measurements are not run,
but it was being logged that they're run

that would be shown at info level.

The time it took to run prioritize function is not relevant for
the operator.
After several days, prioritiy would be adjusted for many relays,
so don't log it.
We can have different debug verbose levels in the future.

based on Torflow's documentation.

Closes bug #28647. Bugfix v0.4.0

Fixes bug #28762. Bugfix v1.0.0.

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.

When parsing results support old ones without new bandwidth
attributes, as descriptor bandwidth burst, consensus_bandwidth
and consensus bandwidth is unmeasured.