GitLab

When generating the Bandwidth File as Torflow, use 28 days of past raw
measurements instead of 5, by default.
Also keep the raw measurements for that long before compressing or
deleting them.
And stop checking whether the compression and delete
periods are valid, without checking defaults first and based on
arbitrary values.

Closes: #40017

fix: doc: Sphinx warnings when creating documentation

Closes #40036

See merge request !54

This should give us at least a clean html, text, and man build
experience.

Closes #40036.

It was referenced by 6e6a8f3b. Since that
image was wrong, created a new screenshot from the current "past 90
days" at consensus-health.tpo.

as this might cause many circuit errors.
They're already added to the generator.
Also adapt the number in test_init_relays.

Closes: #40037.

Happy solstice! :)

fix: doc: Update values in config_tor.rst + clean-up

Closes #40035

See merge request !49

Move initialization via existing socket to this new function and start
tor only when it fails.

Closes: #33150.

to check whether the external control port configuration is set.
There is no need to assert all argument options nor to return the error.

because when trying to connect to an external tor (chutney), it does
not make sense to start own tor.
Also log how the connection has been made.

via control port.

Closes #40035.

fix: doc: Update default values in man_sbws.ini.rst

Closes #40034

See merge request !46

Closes #40034.

fix: doc: Clean up config.rst

Closes #40033

See merge request !45

Closes #40033.

if it fails to be measured as entry.

Mayb closes: #40029.

that could be also checked, increasing the chances that the exit can
exit to our Web servers.
But if it could not, then we need to retry to measure it as 1st hop.

setting it to the default, 60secs.
Since many relays fail to be measured cause of circuit timeout.

Maybe closes #40029.

and make argument optional.

Since sbws is only building 2 hop paths, there is no need to add random
relays to the path, or convert back and forth between fingerprint and
``Relay`` objects.

This will eliminate the circuit errors:
- Tor seems to no longer think XXX is a relay
- Can not build a circuit, no path.
- Can not build a circuit with the current relays.
If a relay is not longer running when attempting to build the circuit,
it will probably fail with one of the other circuit errors: TIMEOUT,
DESTROYED or CHANNEL_CLOSED.

Closes: #40027

after removing KeyValue recent_measurement_attempt_count in #40023.
Changed also torspec, issue #20.

Closes: #40026.