<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-circmgr/src/lib.rs, 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-07T15:50:04Z</updated>
<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>*: suppress cognitive_complexity warnings from nightly</title>
<updated>2025-05-29T14:21:17Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-05-21T14:48:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5327d3e22a83b8469a5d4191d92e1364344ddc93'/>
<id>urn:sha1:5327d3e22a83b8469a5d4191d92e1364344ddc93</id>
<content type='text'>
Apparently clippy nightly is better (or worse?) about detecting
complex functions than before, so I'm suppressing these warnings
where they occur.

I have mixed feelings about these warnings:  On the plus side,
they really do help to detect functions that are twistier than they
need to be.  On the minus side, they get confused by tracing macros,
and the "allows" do pile up.  But on the plus side, those "allows"
do provide a way to find functions that need to be refactored,
and they are never uglier than the functions they decorate.
</content>
</entry>
<entry>
<title>circmgr: Propagate Option&lt;HsCircKind&gt; down to path selection functions</title>
<updated>2025-05-20T19:22:08Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-05-20T14:37:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5527ff8949600d05442daf667fa314a9eeb5ddf2'/>
<id>urn:sha1:5527ff8949600d05442daf667fa314a9eeb5ddf2</id>
<content type='text'>
We'll need this in order to build paths that are specifically
for client rend circuits.  I thought of using a boolean here,
but that had potential to get ugly in the future.
</content>
</entry>
<entry>
<title>circmgr: Make path module public on "--features=experimental-api"</title>
<updated>2025-05-05T18:08:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-05-05T18:05:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4d61218376f64a5a42bc76ffcabda34a14b5fcd9'/>
<id>urn:sha1:4d61218376f64a5a42bc76ffcabda34a14b5fcd9</id>
<content type='text'>
Back in 4c1eb94173521bc5104449327650e20ffe32afa7, for sensible
reasons, we made `tor_circmgr::path` a crate-private module.  But
when we did that, we lost the ability for callers to construct
circuits with custom paths.

This will make it possible for callers to build custom circuits
again, without committing to a very-long-term API for that.

Closes #1981.
</content>
</entry>
<entry>
<title>squash! Upgrade rand dependency to 0.9.</title>
<updated>2025-03-18T16:09:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-18T13:01:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2f8993c22c2b86010e4fd8b5169ef0ab83f8c754'/>
<id>urn:sha1:2f8993c22c2b86010e4fd8b5169ef0ab83f8c754</id>
<content type='text'>
- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`
</content>
</entry>
<entry>
<title>circmgr: Remove the CircParameters build .expect()</title>
<updated>2025-01-16T14:16:01Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2025-01-15T15:46:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ea59eb5a2137a06dbe66f3034d247ff502d9232d'/>
<id>urn:sha1:ea59eb5a2137a06dbe66f3034d247ff502d9232d</id>
<content type='text'>
Instead, return an error and make all call site handle it.

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>circ: Specialize the circparams from netparams function</title>
<updated>2025-01-16T14:16:01Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2025-01-15T14:41:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9e7f59968f7ed07d18b152d6730efa43fc15ae33'/>
<id>urn:sha1:9e7f59968f7ed07d18b152d6730efa43fc15ae33</id>
<content type='text'>
Congestion control parameters have specific values depending on the
circuit type. Instead of using a CircuitType, which is removed in this
commit, specialize the function in this case onion and exit.

This allows us to get rid of CircuitType and solely use TargetCircUsage
instead.

At this commit, we use .expect() on the Builder. Future commit will
remove this to return a Result in case of failure. Worth noting that we
don't expect one.

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>circmgr: Modify CircParameters for congestion control</title>
<updated>2025-01-16T14:16:01Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2024-04-30T14:35:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5917b347fc726a23a83cc4251082acd6962218e8'/>
<id>urn:sha1:5917b347fc726a23a83cc4251082acd6962218e8</id>
<content type='text'>
The congestion control parameters are created from the consensus
parameters (netparams) and then put into the CircParameters object that
is then passed down the tor-proto crate.

Because different parameters are selected depending on the circuit type
(onion vs exit vs sbws), a CircuitType enum is introduced for the sole
purpose of being used to select the right parameters.

Related #534

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>clippy: deny `mod_module_files`</title>
<updated>2025-01-06T23:09:41Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-01-06T23:02:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=252a3a803b2db65792db5bd51dee8950d8557e0d'/>
<id>urn:sha1:252a3a803b2db65792db5bd51dee8950d8557e0d</id>
<content type='text'>
Denies 'mod.rs' files for consistency.

https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files
</content>
</entry>
<entry>
<title>add_warnings, *: Allow clippy::needless_lifetimes</title>
<updated>2024-12-03T14:27:26Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-12-03T14:15:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=64cc3f2ed3eea0b7c5cc89ae07cbdadfdc1646fb'/>
<id>urn:sha1:64cc3f2ed3eea0b7c5cc89ae07cbdadfdc1646fb</id>
<content type='text'>
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.
</content>
</entry>
</feed>
