<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-memquota/src, branch arti-v1.7.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.7.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.7.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-09-29T19:30:03Z</updated>
<entry>
<title>Remove "doc_auto_cfg" incantation from all crates.</title>
<updated>2025-09-29T19:30:03Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-09-29T18:30:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=808b0ec2e3735a6dbbebeb857a3d6040ae02c697'/>
<id>urn:sha1:808b0ec2e3735a6dbbebeb857a3d6040ae02c697</id>
<content type='text'>
This feature has been removed from nightly, in favor of doc_cfg.
</content>
</entry>
<entry>
<title>Migrate to waker noop</title>
<updated>2025-09-22T14:00:53Z</updated>
<author>
<name>disha</name>
<email>dishatantia18@gmail.com</email>
</author>
<published>2025-09-22T14:00:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=698e51e40336b3b01387ac3cd5da629114134251'/>
<id>urn:sha1:698e51e40336b3b01387ac3cd5da629114134251</id>
<content type='text'>
</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>tor-memquota: moved auto calc into separate function</title>
<updated>2025-07-31T15:19:18Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-07-30T20:21:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9fcfda8f52d2e6c1375707fe42f932f813d7e85d'/>
<id>urn:sha1:9fcfda8f52d2e6c1375707fe42f932f813d7e85d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-memquota: return an error when `total_available_memory()` fails</title>
<updated>2025-07-31T15:19:18Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-07-30T19:31:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=41be937debee794cd51a93aef16fc3b0f9e68067'/>
<id>urn:sha1:41be937debee794cd51a93aef16fc3b0f9e68067</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-memquota: small fmt change to log message</title>
<updated>2025-07-31T15:19:18Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-07-29T21:46:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=10eb34b2c23d9fd50e5862226f73fafa154f0648'/>
<id>urn:sha1:10eb34b2c23d9fd50e5862226f73fafa154f0648</id>
<content type='text'>
All other INFO log lines emitted when arti starts begin with an
uppercase character, so this line looks out of place if it begins with a
lowercase character.
</content>
</entry>
<entry>
<title>tor-memquota: change behaviour of "auto"</title>
<updated>2025-07-31T15:19:18Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-07-29T21:39:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9d4a92901884be832b45bf070d614bfeebd185e1'/>
<id>urn:sha1:9d4a92901884be832b45bf070d614bfeebd185e1</id>
<content type='text'>
A `max` of "auto" (the default) now determines a limit based on the
system's total available memory, rather than acting as "disabled".
</content>
</entry>
<entry>
<title>tor-memquota: config now supports `ExplicitOrAuto`</title>
<updated>2025-07-31T15:19:18Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-07-29T20:46:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=53458533a2883e0d0b0eabcf475f72b132770ffd'/>
<id>urn:sha1:53458533a2883e0d0b0eabcf475f72b132770ffd</id>
<content type='text'>
Note that this contains a breaking change to the `ConfigBuilder`. This
should not break any existing toml configuration files.
</content>
</entry>
</feed>
