in RelayList:
- Rename consensus_timestamps to recent_consensus
- Rename recent_consensus_count to recent_consensus when there is
  no counting
- Use the timestamps class to manage/count consensuses
- Remove method not needed anymore

Update relay status before updating the consensus timestamps
Timestamps that are not old yet were getting removed because the
document.valid_after timestamp was still the one from the previous
consensus.

Closes #33570.

since the logic is the same and the there were two bugfixes on the
same logic.

by default days is passed to timedelta, what was making the oldest
date be thousands of days in the past.

Bugfix 1.1.0.

Fix linter error after merging #30733 and #30727.

Closes: #33199.

Keep the relays that are not in the the last consensus, but are not
"old" yet.

Closes: #30727

when fetching new consensuses.

Part of #30733.

and useless descriptors, so that sbws detect early changes in the relay
descriptors and continue downloading them even when Tor is idle.

Closes: #30733. Bugfix v0.2.0.

Instead:
* use the consensus valid-after time, or
* use the supplied timestamp, or
* warn and use the current time.

This should fix the occasional CI failure, when the current time is 1 second
later than the test consensus time. (Or it should warn, and we can fix the
test code.)

Fixes bug 30909; bugfix on 1.1.0.

measuring unique relays.
Create new module heartbeat.

Closes: #28652

and number of times in a priority list attrs and methods,
to be able to store the data.
Part of #28567.

Since all the other bandwidth values are in bytes and sbws should
work with bytes until it generates the final `bw`.

Closes: #29707. Bugfix v1.0.3.

used in the bandwidth file, so that it is less confusing and less
prone to errors.

to the state file.
To know the total number of consensus seen in the last days.

Part of #28566.

that have been seen for a relay and for the relay list.

Part of #28566.

for each relay and for the list of relays when fetching new
network statuses.
To count the number of times a relay was in a consensus and how
many consensuses have been seen.
In the test network router status entries don't have document
attribute.
Part of #28566

When the descriptor or network status of a relay was not obtained,
some attributes can't be obtained it can be return None instead
of failing the measurement.
Also, there's no need for hasattr when getattr can just return
None as default.

Closes #28870. Bugfix v0.4.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.

In order to use it in torflow's scaling method

The flags are: not having a badflag and the policy allows to exit
to a port.

The flags are: not have the badflag and the policy allows to exit
to a port.

The flags are: not having a badexit and the policy allows to exit
to a port.

In order to do not relay on resolving a domain locally to check
the IP in the exit policy.

Even for a valid domain that usually resolves, sometimes the local DNS
resolver won't be able to resolve it (duh). Catch the exception that gets
thrown in that instance and fail gracefully by returning an empty list.

GH: closes #218

Matt Traudt authored Jun 22, 2018 and juga committed Jun 24, 2018

The chance of us needing a refresh at this point is TINY, but it's probably
better to return a list of relays stale by a millisecond than it is to cause
the user's program to crash.