<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-chanmgr/src/mgr.rs, branch arti-v2.0.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.0.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.0.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-01-22T16:16:44Z</updated>
<entry>
<title>relay: Pass advertised addresses to the channel handler</title>
<updated>2026-01-22T16:16:44Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2026-01-14T19:17:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=05c703d7b510f7356be1ec9f0cd62735d7fcee78'/>
<id>urn:sha1:05c703d7b510f7356be1ec9f0cd62735d7fcee78</id>
<content type='text'>
We need the advertised addresses for the NETINFO cell when opening a
relay channel. Keep them in the TorRelay object so we can pass them to
the ChanMgr channel handler.

This will also help with config reload where only the local values in
TorRelay will need to be updated.

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>chanmgr: Get rid of the builder outbound_chan_type</title>
<updated>2026-01-13T18:46:18Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2026-01-08T17:31:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9e359a4e2d5671faeb1471f9f8c945ef9ebf5e07'/>
<id>urn:sha1:9e359a4e2d5671faeb1471f9f8c945ef9ebf5e07</id>
<content type='text'>
Instead, we'll simply use `RelayInitiator` if the identity keys
(identities) struct is set.

This avoids the problem where someone could call outbound_chan_type() of
the ChanMgrConfig and get the wrong channel type if with_identities() is
set after.

This way, a single call, `with_identities()` is what will define the
outbound channel type so no chance of errors.

This also removes the cfg_if {} around the builder creation in a much
more simplified version.

Related to #1599

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>chanmgr: Add ChannelType to channel manager config</title>
<updated>2026-01-13T18:46:17Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2025-12-16T18:15:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bbb3785f80da837a5c1e86845cdf6f80668625a3'/>
<id>urn:sha1:bbb3785f80da837a5c1e86845cdf6f80668625a3</id>
<content type='text'>
This allows us to pass it to the ChanBuilder which will be able to use
this type for the outbound channels.

For now, we do this trick where if we have relay identities, we always
consider that all outbound channels will be RelayInitiator.

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>chanmgr: Introduce a ChanMgrConfig struct</title>
<updated>2026-01-13T18:45:24Z</updated>
<author>
<name>David Goulet</name>
<email>dgoulet@torproject.org</email>
</author>
<published>2025-12-16T17:56:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0eb2e1d5ef74e26114a85f4827991c5bea7b20b9'/>
<id>urn:sha1:0eb2e1d5ef74e26114a85f4827991c5bea7b20b9</id>
<content type='text'>
This struct is used to pass configuration parameters to the ChanMgr when
building it.

At the moment, it holds the ChannelConfig and RelayIdentities (feature
gated) which will be used in subsequent commits.

Note that relays do require RelayIdentities to build channels.

Signed-off-by: David Goulet &lt;dgoulet@torproject.org&gt;
</content>
</entry>
<entry>
<title>opentelemetry: Instrument a bunch of functions.</title>
<updated>2025-11-24T16:28:07Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-11-24T16:28:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a4db6a7495b13dd7b00416dd1660a5ad82b60919'/>
<id>urn:sha1:a4db6a7495b13dd7b00416dd1660a5ad82b60919</id>
<content type='text'>
These are all aimed at figuring out in more detail what's going on
in #2079 and related issues.
</content>
</entry>
<entry>
<title>Merge branch 'relay-bin-4' into 'main'</title>
<updated>2025-11-11T22:34:10Z</updated>
<author>
<name>opara</name>
<email>opara@torproject.org</email>
</author>
<published>2025-11-11T22:34:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=70bef2ab911239ed2a13ec1a6cfc0009f8031bef'/>
<id>urn:sha1:70bef2ab911239ed2a13ec1a6cfc0009f8031bef</id>
<content type='text'>
arti-relay: Add OR port listener task

See merge request tpo/core/arti!3396</content>
</entry>
<entry>
<title>Fix name of clippy lint to unchecked_time_subtraction (2)</title>
<updated>2025-11-06T11:28:22Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-11-06T11:23:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a5fd5c48ea059a80cc1f6c50e248654b5ff3aaff'/>
<id>urn:sha1:a5fd5c48ea059a80cc1f6c50e248654b5ff3aaff</id>
<content type='text'>
Run maint/add_warning
</content>
</entry>
<entry>
<title>tor-chanmgr: wrap the peer address in `Sensitive`</title>
<updated>2025-11-05T19:31:01Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-10-28T05:06:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=de760f8049b901e0d99c345a700523b8e8b3cc25'/>
<id>urn:sha1:de760f8049b901e0d99c345a700523b8e8b3cc25</id>
<content type='text'>
For incoming connections, wrap the peer address in `Sensitive` as it
could be a client.
</content>
</entry>
<entry>
<title>opentelemetry: Add some instrument macros.</title>
<updated>2025-09-24T19:23:32Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2025-09-16T13:25:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e21ebd3793d497429ba7c8c437b346a9a2833407'/>
<id>urn:sha1:e21ebd3793d497429ba7c8c437b346a9a2833407</id>
<content type='text'>
I've added these in places that are useful for the debugging that I've
been doing.
</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>
</feed>
