mirrors/arti.git/crates/tor-netdir/src/lib.rs, branch arti-v1.4.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.22025-03-25T12:05:56Znetdir: 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.
netdir: Another test for choose_multiple_weighted.2025-03-25T12:05:56ZNick Mathewsonnickm@torproject.org2025-03-24T12:57:02Zurn:sha1:8c411a9d7394477cc9ad4dc6b5f3813cbe23a359
Here we test the (arguably inconsistent behavior) where can we
return fewer items than requested if no item had zero weight.
(If this ever becomes an error, we need to modify the calling code.)
netdir: Warn on unexpected WeightedErrors2025-03-25T12:05:56ZNick Mathewsonnickm@torproject.org2025-03-24T12:49:54Zurn:sha1:80553fb534303f7a10c34c5a52b90ae875eb0620
WeightedError::InsufficientNonzero is expected under some
circumstances, but the other instances would mean that we have a
bug.
netdir: add a test to verify weighted sampling2025-03-25T12:05:56ZNick Mathewsonnickm@torproject.org2025-03-24T12:34:36Zurn:sha1:69bf56db10dfc9ab439360c24e34988316630856
We want to make sure that behavior for 0-weighted elements is
consistent for choose_multiple_weighted and choose_weighted.
tor-netdir: Handle InsufficientNonZero error.2025-03-20T19:06:50ZNick Mathewsonnickm@torproject.org2025-03-20T19:06:50Zurn:sha1:a4ef9d0677f1e6b873189b8cd7360bec31a8edd9
Possible fix for #1902.
squash! Upgrade rand dependency to 0.9.2025-03-18T16:09:44ZNick Mathewsonnickm@torproject.org2025-03-18T14:26:16Zurn:sha1:0805d27122b929f2eaa75f56761cb0da210d5b13
- Several methods have been moved out of SliceRandom.
squash! Upgrade rand dependency to 0.9.2025-03-18T16:09:44ZNick Mathewsonnickm@torproject.org2025-03-18T13:02:40Zurn:sha1:e57c16e03ddf07dffaa4dda4fa1b4101ac02a233
- The rand::distributions module has been renamed to rand::distr
netdir: Consider RelayFamilyIds based on family rules2025-02-25T14:29:50ZNick Mathewsonnickm@torproject.org2025-02-10T21:10:15Zurn:sha1:9650d0b75d6a5ce5c554cb0ac04077374a889538
This implements the client side of proposal 321.
It's a breaking change in netdir, since in_same_family now takes an
extra argument.
relay-selection: Add FamilyRules to exclude_relays_in_same_family.2025-02-25T14:29:50ZNick Mathewsonnickm@torproject.org2025-02-10T20:51:36Zurn:sha1:5ce84e59b6031416a7d404d20c3a2efce0ec5f2a
When we're trying to exclude relays by family,
we need to know which lists to look at.
This information ultimately comes from the network parameters.
We could avoid this change if we just told clients
"look at all family information all the time",
but that's not what the proposal says.
This is a breaking change.
clippy: deny `mod_module_files`2025-01-06T23:09:41ZSteven Engleropara@torproject.org2025-01-06T23:02:49Zurn:sha1:252a3a803b2db65792db5bd51dee8950d8557e0d
Denies 'mod.rs' files for consistency.
https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files