<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdir/src/lib.rs, branch arti-v1.5.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-08-26T09:41:21Z</updated>
<entry>
<title>tor-netdoc: Combine ConsensusRouterStatus and GenericRouterStatus</title>
<updated>2025-08-26T09:41:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-21T09:34:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7bde61567649ea93e03a7ad63e94a949319c9f03'/>
<id>urn:sha1:7bde61567649ea93e03a7ad63e94a949319c9f03</id>
<content type='text'>
Now we only need one type.
</content>
</entry>
<entry>
<title>tor-netdoc: Abolish RouterStatus trait in favour of generic methods</title>
<updated>2025-08-26T09:41:21Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-08-20T15:30:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d66325643fa72921603cb08c84f6f74224f96cfc'/>
<id>urn:sha1:d66325643fa72921603cb08c84f6f74224f96cfc</id>
<content type='text'>
Our approach to sharing code between md and plain consensuses is now
the new "variety" system, not generics.
</content>
</entry>
<entry>
<title>Fix warnings and errors from edition 2024.</title>
<updated>2025-08-07T15:28:39Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-06T01:54:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4fbbffe7c14b2df6290268b6e3c8530106ab2529'/>
<id>urn:sha1:4fbbffe7c14b2df6290268b6e3c8530106ab2529</id>
<content type='text'>
The two main causes of errors were:

- Since some of the lifetime rules have changed, we no longer need
  to do as many "bind a variable and immediately return it"
  patterns, and so clippy now warns about them.
- We needed to adjust the explicit captures (`use&lt;...&gt;`)
  in a couple of our RPIT instances.
</content>
</entry>
<entry>
<title>Switch Cargo.toml files to edition 2024.</title>
<updated>2025-08-07T15:28:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-06T01:19:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=77b0de43b8c67cdb81befe0680a3df43b6ad37bc'/>
<id>urn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc</id>
<content type='text'>
First, run

```
git grep -l "^edition =" |
    xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```

Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.

Third, run cargo fmt again.
</content>
</entry>
<entry>
<title>Fix errors from rustdoc nightly.</title>
<updated>2025-08-05T13:34:23Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-05T13:34:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=30a36b17593c10255ddd37eb7579c895c6629b67'/>
<id>urn:sha1:30a36b17593c10255ddd37eb7579c895c6629b67</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Typo fixes (automatic and hand-verified)</title>
<updated>2025-07-09T16:27:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-07-09T16:27:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fd24caa9959a4e9a04ad10cc047975b8566a884b'/>
<id>urn:sha1:fd24caa9959a4e9a04ad10cc047975b8566a884b</id>
<content type='text'>
Made with https://crates.io/crates/typos-cli
</content>
</entry>
<entry>
<title>Temporarily suppress mismatched_lifetime_syntaxes.</title>
<updated>2025-07-07T15:50:04Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-07-07T15:50:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a11b611466a5a73f5e06a0aabd17284a57d12fe3'/>
<id>urn:sha1:a11b611466a5a73f5e06a0aabd17284a57d12fe3</id>
<content type='text'>
See #2060.
</content>
</entry>
<entry>
<title>proto: Move NegotiatedHopSettings to a higher level</title>
<updated>2025-06-10T15:52:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-06-05T16:11:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e07000a2ea86f1205ed9dc44228c0b2c69f1a36b'/>
<id>urn:sha1:e07000a2ea86f1205ed9dc44228c0b2c69f1a36b</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>NetDir::pick_n_relays: avoid some unwarranted warnings</title>
<updated>2025-06-05T21:42:23Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-06-05T21:17:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=044011474d5613e1ab314659f373ac852a31d221'/>
<id>urn:sha1:044011474d5613e1ab314659f373ac852a31d221</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>tor-netdir: Warn on one more case of insufficient items</title>
<updated>2025-04-29T22:52:39Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-04-29T19:25:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ad2560e2efb80cc44b09d15eff0c761857142ac7'/>
<id>urn:sha1:ad2560e2efb80cc44b09d15eff0c761857142ac7</id>
<content type='text'>
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.
</content>
</entry>
</feed>
