| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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_ :)
|
| |\
| |
| |
| |
| | |
various crates: MSRV TODO standardization and cleanup of an old TODO
See merge request tpo/core/arti!2945
|
| | |
| |
| |
| |
| | |
- https://github.com/rust-lang/rust-clippy/issues/11764 was fixed upstream, so
this is no longer needed.
|
| | |
| |
| |
| |
| | |
This name reflects its purpose better than the original one,
since it includes required protocols as well as recommended ones.
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
Instead of doing the more sensible thing when every relay has weight
0, give a warning message.
|
| | |
|
| |
|
|
|
|
| |
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.)
|
| |
|
|
|
|
| |
WeightedError::InsufficientNonzero is expected under some
circumstances, but the other instances would mean that we have a
bug.
|
| |
|
|
|
| |
We want to make sure that behavior for 0-weighted elements is
consistent for choose_multiple_weighted and choose_weighted.
|
| |
|
|
| |
Possible fix for #1902.
|
| |\
| |
| |
| |
| |
| |
| | |
protover: Add support for subprotocol version mnemonics.
Closes #1891
See merge request tpo/core/arti!2854
|
| | | |
|
| | |
| |
| |
| | |
- The Rng::gen() functions have been renamed to Rng::random().
|
| | |
| |
| |
| | |
- Several methods have been moved out of SliceRandom.
|
| |/
|
|
| |
- The rand::distributions module has been renamed to rand::distr
|
| |
|
|
|
|
|
| |
This implements the client side of proposal 321.
It's a breaking change in netdir, since in_same_family now takes an
extra argument.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Related #534
Signed-off-by: David Goulet <[email protected]>
|
| |
|
|
|
|
| |
These are tentative, so I haven't added them to param-spec yet.
Part of #1729
|
| |
|
|
|
|
| |
Denies 'mod.rs' files for consistency.
https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files
|
| |
|
|
| |
These are new in Rust 1.83.
|
| |
|
|
|
|
|
|
| |
In 1.83, this warning triggers on many of our crates.
We're thinking of fixing them all, but for now,
we're going to disable the warning.
This is part of #1765.
|
| | |
|
| |
|
|
|
| |
These helpers seem potentially broadly useful, and only really
discoverable if they're here.
|
| |
|
|
| |
netdirs (fmt).
|
| |
|
|
|
| |
This allows us to set SRVs for example (needed because by default, the
test `NetDir` is built from a consensus that doesn't contain any SRVs).
|
| |
|
|
|
| |
This warning complains when we say `where T: SomeTrait + ?Sized`
when `SomeTrait` is inherently Sized.
|
| |
|
|
| |
This commit is automatically generated.
|
| |
|
|
|
|
| |
The old code produced a warning from clippy nightly; we may as well
update to use the new associated consts. (They've been there since
Rust 1.4x.)
|
| |\
| |
| |
| |
| |
| |
| | |
tor-guardmgr: Make lite vanguards work
Closes #1275 and #1340
See merge request tpo/core/arti!2075
|
| | |
| |
| |
| |
| | |
`TestNetDirProvider::set_netidr_and_notify` blocks if the
channel is full, so let's give it a non-zero size.
|
| | | |
|
| | |
| |
| |
| |
| | |
Previously they were a bit confusing, and the public function
explained its behavior in terms of the private one.
|
| |/
|
|
|
|
|
| |
Explain that `by_ids` isn't what you want if you need to know
whether a relay _definitely_ doesn't exist.
Closes #1365
|
| | |
|
| |
|
|
| |
This was an open-coded specialisation. Remove the one call site.
|
| | |
|
| | |
|
| |
|
|
|
| |
Everybody outside of tor-netdir should use
HasRelayIds::same_relay_ids, whose intent is clearer.
|
| |
|
|
| |
These were only used for testing.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
In *RelayDetails, this is just a matter of changing a bunch of
`self`s to `self.0`.
Additionally, I've added temporary stub functions to delegate to the
new functions.
|
| |
|
|
| |
This is 99% code movement.
|