GitLab

fix: doc: Clarify Torflow aggregation

Closes #40082

See merge request !80

Closes #40082.

because Torflow is not using them by relay type.

This reverts commit fc3d3b99 and partialy
reverts a82c2618.

It was a mistake to think torflow was using the means by relay type,
it actually sets the same networks means for all relay types.

Closes #40080.

Closes #33599.

Closes: #40070

black insists to keep one long line and flake complain, therefore make
flake to ignore it.

Also:
- Update versioneer
- And include other source distribution files in MANIFEST.in
- Add project URLs
- Add formatter and linter dependencies and configurations.
- tox: Remove travis, fix python environments
- tox: Remove extra coverage options and add them in .coveragerc.

also uncomment final newline. Can be commented again in case it fails

Calculate network stream and filtered bandwidth averages per relay
type, to obtain bandwidth weights the same way as Torflow.

Closes #40059.

since they are used as the numerator when calculating the ratio and the
rounding already returns a minimum of 1.

it should not be the case because the measurements come from
successful results, but otherwise it'd throw an exception.

because Torflow does it.

After refactoring in #40041, it was forgotten to return the error in
the case a helper was not found, what can happen in test networks.

Closes #40065.

and fix test that didn't consider that there might be other logs from
other threads.

Closes #33797.

not only the times that are not kept.

Closes #40060

also change formatting to show thread.

when it contains sensitive information.

when they contain sensitive information, eg. Web server or are too
verbose for the debug level.
Also add log to indicate when the main loop is actually started.

to the relay consensus timestamps list, so that it can be
tested it was in a concrete consensus.

when any of the commands fail.