<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdir, branch arti-v1.4.5</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.5</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.5'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-07-07T17:41:41Z</updated>
<entry>
<title>Bump all the unstable tor- and arti- crates to 0.32.0.</title>
<updated>2025-07-07T17:41:41Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-07-07T17:26:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=721568b1bf261f6635c61c9f3abe52e24af1bf9c'/>
<id>urn:sha1:721568b1bf261f6635c61c9f3abe52e24af1bf9c</id>
<content type='text'>
Done using:

```
for crate in $(./maint/list_crates  | rg '^(tor|arti-)'); do
    cargo set-version -p $crate 0.32.0
done
```
</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>NetParameters::saturating_update: log when a value is out of range</title>
<updated>2025-06-23T17:11:01Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-06-10T22:01:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2d79634258326e7f86471fe2b2720f83d215c2cc'/>
<id>urn:sha1:2d79634258326e7f86471fe2b2720f83d215c2cc</id>
<content type='text'>
On one hand, this can be quite noisy when something *is* out of range.
On the other hand, a clamped value shouldn't normally happen, and is
likely to result in surprising and otherwise difficult-to-debug
behavior.
</content>
</entry>
<entry>
<title>Log unrecognized net params</title>
<updated>2025-06-23T17:11:01Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-06-10T21:24:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=00fbefa2a70a72bd3193e098790219c6cb879858'/>
<id>urn:sha1:00fbefa2a70a72bd3193e098790219c6cb879858</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'hs-interval-min' into 'main'</title>
<updated>2025-06-11T01:04:54Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-06-11T01:04:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0a677a9b42558f23ceb1d46e6ee1d4251bd8acd7'/>
<id>urn:sha1:0a677a9b42558f23ceb1d46e6ee1d4251bd8acd7</id>
<content type='text'>
tor-netdir: decrease minimum hsdir_interval from 30 to 5

See merge request tpo/core/arti!3042</content>
</entry>
<entry>
<title>tor-netdir: decrease minimum hsdir_interval from 30 to 5</title>
<updated>2025-06-10T21:00:11Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2025-06-10T21:00:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ba2247dfa42a6230c044ac23e631f5750b6f847b'/>
<id>urn:sha1:ba2247dfa42a6230c044ac23e631f5750b6f847b</id>
<content type='text'>
This matches the spec change:
&lt;https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/406&gt;

Progress on:
&lt;https://gitlab.torproject.org/tpo/core/chutney/-/issues/40038&gt;
</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>Un-pin version of typed-index-collections</title>
<updated>2025-06-09T23:26:19Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-06-09T23:26:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0978e592d0e41e3628070f5464925b29f0ff14fd'/>
<id>urn:sha1:0978e592d0e41e3628070f5464925b29f0ff14fd</id>
<content type='text'>
Now that our MSRV has been updated to 1.83, we should be able to get
away with this.

Closes #1647.  Reverts !2471.
</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>release: Bump all tor-/arti- crates to 0.31.0.</title>
<updated>2025-06-05T10:33:57Z</updated>
<author>
<name>Alexander Hansen Færøy</name>
<email>ahf@torproject.org</email>
</author>
<published>2025-06-05T10:33:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=95180f80d7ab574a95368f3bca1e7b78555d479a'/>
<id>urn:sha1:95180f80d7ab574a95368f3bca1e7b78555d479a</id>
<content type='text'>
This was done using:

for crate in $(./maint/list_crates | grep -P '^tor-|^arti-'); do
        cargo set-version -p $crate 0.31.0
done
</content>
</entry>
</feed>
