before stopping the scanner.

We changed conf['paths']['X'] to use conf.getpath('paths', 'X'),
so that paths with `~` get expanded, but cleanup was forgotten.
Also remove extra path check in main.
And run cleanup as part of the integration tests.

Bugfix v0.7.0.

Exit the scanner with error stoping threads first when there is not
any functional destination, since the destinations can not be recovered.
After merging #28897, `stop_threads` can be used (instroduced in #28869).

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.

in every measurement.
This removes the need for an extra lock for every measurement
It should also not be depending on a time interval, but on the
number of failures detected.
Not counting number of failures since it would need to modify the
destination or list of at runtime. It should be done in a future
refactor.

Fixes bug #28897. Bugfix v0.3.0

after finishing the first loop.
As noted in bug28933_01.

The bandwidth file is generated only with relays that have some
successful measurements, but we forgot to load all results
(including the relays with failed measurements) after we started
to include the number of failure measurements in each relay
bandwidth line.

Closes #29568. Bugfix v0.4.0 (line introduced in v0.1.0).

Merge: 8dbe8905.
Coded introduced in a550d731 and
5dae9b99.

Closes: #29149. Bugfix v0.1.0.

that depends on the HTTP request timeout.

since the relay might start being measured some time after
apply_async is called if there're not available threads.

also split main function into an extra main_loop function to be
able to stop the threads after they have started.
Also check end event in the mean loop and before starting to
measure a new relay.

Fixes bug #28869. Bugfix v0.1.0.

so that the objects that manage the threads can be stop at any
time.

when worker thread finish.

instead of bandwidth.
Forgotten when bandwidth was renamed to consensus_bandwidth in
9e089b72.

In order to run the scanner as part of the integration tests.

When sbws stalls after the prioritization loop waiting for thread
results, give it some minutes and otherwise log the backtrace.
This way if there's any bug or deadlock, operators can help to
debug it.

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.

create a constant, set the headers in the session.

to their values instead of have to extra functions to call
in every request.
This also makes the code more clear.

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.

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

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