If mean or median argument is empty, they throw an exception.
This can happen when the scanner has stopped and the result is
stored as successful without any downloads.

Closes: #40012

Closes: #33473

Closes: #40011

juga authored Aug 01, 2020 and Georg Koppen committed Aug 11, 2020

Conversion only happens when parsing a bandwidth file in the
integration tests.

Closes: #40009

when checking exit policies to know whether an exit can exit to a port.

Closes: #40010

Change the version from which the release script is used.
Also explain the prefixes used in the commits.

Closes #29294

it should not take more effort than solving self-sbws issues.

since it is now managed automatically by versioneer.
Instead, suggest creating a "next" maintainance branch.
But stop using `-` and `.` characters in it, to type it faster, since
most of the new branches will be based on it.

since now sbws version is calculated from last release tag.

Since it is now done by `versioneer`.

releases can live now in gitlab.tpo, instead of github.com and
there is no need to check them since Gitlab is FLOSS and gitlab.tpo is
hosted by Tor Project.

Also, stop assuming which is the current branch and remote and do not
push. Instead guide the maintainer to do it.

Replace also Github terminology to Gitlab.

Closes: #40001

Closes: #40007

to vote on approximately the same numbers of relays as Torflow.
Torflow does not exclude relays with few or close measurements, though
it is possible that because of the way it measures, there are no few
or close measurements.

Closes #34393

When an exit policy allows to exit only to some subnet, it is not
enough to check that it can exit to a port, since it can, but it might
not be able to exit to the domain/ip of the sbws Web servers.
To ensure that without having to check whether it can exit to a
specific domain/ip, we can query the exit policy with `strict`.

Closes #40006. Bugfix v1.0.3.

fix: tests: Create new authority keys

Closes #33150 and #34394

See merge request tpo/network-health/sbws!10

Previously, when a relay changes IP, only the measurements with the
last IP were considered.
Relays with dynamic IP could get unmeasured that way.
Now, all the measurements are considered.

Closes: #33832. Bugfix 0.5.0.