mirrors/arti.git/crates/tor-netdir/src/lib.rs, branch arti-v1.4.5mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.52025-07-07T15:50:04ZTemporarily suppress mismatched_lifetime_syntaxes.2025-07-07T15:50:04ZGabriela Moldovangabi@torproject.org2025-07-07T15:50:04Zurn:sha1:a11b611466a5a73f5e06a0aabd17284a57d12fe3
See #2060.
proto: Move NegotiatedHopSettings to a higher level2025-06-10T15:52:28ZNick Mathewsonnickm@torproject.org2025-06-05T16:11:30Zurn:sha1:e07000a2ea86f1205ed9dc44228c0b2c69f1a36b
We will construct this object based on the circuit parameters _and_
on the target's supported protocol versions, so we need to do so
when we have both pieces of info.
NetDir::pick_n_relays: avoid some unwarranted warnings2025-06-05T21:42:23ZJim Newsomejnewsome@torproject.org2025-06-05T21:17:10Zurn:sha1:044011474d5613e1ab314659f373ac852a31d221
Previously we logged a warning whenever `choose_multiple_weighted`
returns `Ok(iter)`, whenever `iter` contains fewer relays than
requested.
However, this is expected behavior of `choose_multiple_weighted` if the
filtered list of relays doesn't have the requested number of relays, in
which case it should return all of the relays in the filtered list.
In particular, this condition occurs regularly in test networks when
looking for candidate relays to add to the potential guard set while
excluding those already in the potential guard set.
We still warn if the returned list is fewer than requested, *and* fewer
than available in the filtered list.
tor-netdir: Warn on one more case of insufficient items2025-04-29T22:52:39ZNick Mathewsonnickm@torproject.org2025-04-29T19:25:23Zurn:sha1:ad2560e2efb80cc44b09d15eff0c761857142ac7
Now that choose_multiple_weighted can once more return
fewer items than requested, we should warn when it does so,
to be consistent with our other cases of warning about #1907.
tor-netdir: test for rand 0.9.1 behavior instead of 0.9.02025-04-29T22:52:34ZNick Mathewsonnickm@torproject.org2025-04-29T19:20:59Zurn:sha1:3b0cef1642702641acb55046792af8aae5a26b8f
Rand 0.9.1 reverted the changes that caused #1903,
in https://github.com/rust-random/rand/pull/1623.
This broke our test that made sure that rand wasn't going to change
their behavior _again_ :)
Rename recommended_protocols to protocol_statuses.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-16T11:59:00Zurn:sha1:461a2467f90dbd2bf4f4b900fc0816aa4c906fdb
This name reflects its purpose better than the original one,
since it includes required protocols as well as recommended ones.
netdir: Add a recommended_protocols() to NetDirProvider2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-07T14:59:29Zurn:sha1:42e01549f946f5f23ab004fe2ed82fc9279d8e8ddirmgr, netdir: Store protocol requirments as soon as they are validated.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-03T15:20:32Zurn:sha1:98f28d0b4c5c2b90ed732ed29d571f71a48c15b4Fix another miscapitalized "MicroDesc"2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-02T17:38:51Zurn:sha1:fdfc4b9fa5ac731e19a99f48cf07c4d441bac101netdir: Add a (hopefully) temporary workaround2025-03-25T12:05:56ZNick Mathewsonnickm@torproject.org2025-03-24T18:46:05Zurn:sha1:57c7a289513e2f0faf0844c6dee7513a59e703f3
Instead of doing the more sensible thing when every relay has weight
0, give a warning message.