<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-ptmgr/src, branch arti-v1.3.2</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.2</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.2'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-01-06T23:09:41Z</updated>
<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>
<entry>
<title>update `CfgPath::path` to use a `CfgPathResolver`</title>
<updated>2024-11-18T15:01:56Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2024-11-05T05:18:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b5aa8f7a88808dc9267457ec723d23c8ffd1295a'/>
<id>urn:sha1:b5aa8f7a88808dc9267457ec723d23c8ffd1295a</id>
<content type='text'>
This is a big change across multiple crates since there isn't a good way
to break it up.

This changes the signature of `CfgPath::path` to:

```
pub fn path(&amp;self, path_resolver: &amp;CfgPathResolver) -&gt; Result&lt;PathBuf, CfgPathError&gt; {
```

Making this change means that our global `CfgPathResolver` needs to be
stored in the 'arti-client' library instead of `tor-config-path`, and
must be passed through to anything that calls `path` to expand the
variables.
</content>
</entry>
<entry>
<title>tor-ptmgr: pass through the `CfgPathResolver`</title>
<updated>2024-11-18T15:01:56Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2024-11-05T05:38:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7a5482ded40134231d0c81c5d7e476f7c5ed7696'/>
<id>urn:sha1:7a5482ded40134231d0c81c5d7e476f7c5ed7696</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-config: removed re-export of `CfgPath`</title>
<updated>2024-11-04T14:58:43Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2024-10-29T19:55:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6b3e0f89c04fed10436f6437b852d6c9671be7df'/>
<id>urn:sha1:6b3e0f89c04fed10436f6437b852d6c9671be7df</id>
<content type='text'>
Also updated other packages to get `CfgPath` directly from
`tor-config-path' instead of 'tor-config'.
</content>
</entry>
<entry>
<title>Use mpsc_channel_no_memquota next to a TODO</title>
<updated>2024-10-15T11:03:18Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-10-09T18:19:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=507342b2119c760e9b79182bc8bfe6a04fee5509'/>
<id>urn:sha1:507342b2119c760e9b79182bc8bfe6a04fee5509</id>
<content type='text'>
We have a ticket for this.  But the ticket number was wrong, so fix that.
</content>
</entry>
<entry>
<title>memquota: Note a TODO about PT channels</title>
<updated>2024-10-02T15:05:12Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-10-01T16:11:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=17b4d312c433c6afa90bb29f09bed799742d5bb4'/>
<id>urn:sha1:17b4d312c433c6afa90bb29f09bed799742d5bb4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ptmgr: Forbid managed pts on non-localhost</title>
<updated>2024-09-25T16:42:45Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-25T16:42:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=51d0888479ee985593e91bdb722f0b8929fd4ca3'/>
<id>urn:sha1:51d0888479ee985593e91bdb722f0b8929fd4ca3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ptmgr: Warn on non-local unmanaged PTs</title>
<updated>2024-09-25T16:35:40Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-25T16:35:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8f94dda85f90d20cd6483916c79f9627604ca12a'/>
<id>urn:sha1:8f94dda85f90d20cd6483916c79f9627604ca12a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>extract tor_async_utils::oneshot into ::oneshot-fused-workaround</title>
<updated>2024-08-28T14:27:46Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2024-08-22T19:20:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=46f7f01092e6ac55e3e958dc3a2228b1d36e26a1'/>
<id>urn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1</id>
<content type='text'>
Having this in the `tor-async-utils` crate prevents us from doing both
of the following without introducing a circular dependency:

* using it in `tor-rtmock` (which we currently do, particularly in
  tests).
* using `tor-rtmock` to test things in `tor-async-utils`. We don't do
  this yet, but it is generally sensible to do so. In particular we
  want to move the `stream_peak` module there, which is currently tested
  with `tor-rtmock`.

Moving this into its own crate avoids this circular dependency.
</content>
</entry>
</feed>
